One connected workflow
Build an outreach process around the tools you actually need: organized contacts, thoughtful writing, configured follow-ups, and a clear place to handle replies.
Import contacts, review individual records, organize lists, and use custom fields for information that matters to your audience. Maintain suppression separately so excluded recipients stay out of eligible campaign sending.
Draft subjects and email bodies, reuse templates, and ask the AI tools for writing or research assistance. Set up an initial email and follow-up steps, then review the audience, account, and schedule before launching.
Review synchronized conversations in the inbox. Supported workflows can act on matching replies and tracking events. Analytics report recorded activity, while deliverability checks help identify configuration issues. Opens and clicks are signals, not proof of human engagement.
Manage team invitations, notification preferences, scoped API keys, and supported webhooks in workspace settings. General webhooks support reply.received and bounce.detected; event delivery is best effort.
Contact management answers who belongs in your audience. Campaigns and sequences answer what should be sent and when. The inbox answers what happened when someone responded. Workflows help apply a supported action consistently after a matching event. Understanding those boundaries makes it easier to choose the right tool instead of expecting one screen to perform the entire process.
For example, a list is an organizational tool, while suppression is a sending exclusion. Removing a contact from a list is not a substitute for an opt-out. Similarly, saving a template stores reusable content; it does not enroll contacts or schedule messages. An AI draft can help you write, but it does not establish that the facts in the draft are correct.
Team and integration features support the same workflow. Invitations provide workspace access according to membership and permissions. Scoped API keys support implemented endpoints. Event webhooks and Slack notifications require valid configuration and only deliver supported events. Before designing an external process around an integration, check the event coverage and account for best-effort delivery.
A practical walkthrough
| What you notice | What to check |
|---|---|
| A workflow never matches | Check its enabled state, conditions, and whether the event contains the required context. |
| A webhook does not arrive | Check the supported event subscription, public HTTPS destination, and delivery history. |
| A duplicated template is not active | Duplicates begin as drafts. Review its subject and body before activation. |
Yes. Supported workflow actions include pausing an enrollment, adding tags, updating a supported status, adding a contact to a list or suppression, and creating an in-app notification.
No. Review the integrations available in your workspace. API access and supported webhooks do not imply a native connection to every CRM.