Send the right message
Connect a contact and content to a send block. The channel, account and allowances depend on your configuration and plan.
Turn data into a concrete next step: send a message, record a CRM note or notify your team. Connect conditions, actions and monitoring in one process.
One follow-up. Three connected actions.

Connect a contact and content to a send block. The channel, account and allowances depend on your configuration and plan.
Create a note linked to the contact and record process steps in the CRM. Notes, tasks, reminders and recaps help you recover context and continue the work.
Notes, tasks and recapsUse workflow conditions to decide when to notify. Push notifications reach enabled workspace colleagues according to the process configuration.
With Agatha
Describe the process and content you need. Agatha helps you prepare workflows and communications; you review recipients, conditions and actions before activating them.
Meet Agatha“Prepare a follow-up: a customer message, a CRM note and a team notification.”
An example tied to this page’s blocks: communication, a CRM record and an internal notification.
Group lists and sub-lists to organise segments and variants of the same campaign. The group overview brings sends, reads, replies and progress together: compare the parts, then open the one that needs attention.
Move from the overall view to members, communications and the monitoring desk. Each contact stays connected to the work ahead.
A list is also an operational view: who needs contact, who has started, who has completed and what happened to communications. The overview connects CRM, surveys and monitoring.

Work with contact lists and prepare communications in the same platform. Email, WhatsApp and Telegram are available according to your plan and connected accounts.
A workflow can prepare a proposal and pause before sending it. An authorised person reviews the context and approves or rejects it. Their decision determines the next branch: for example, send the proposal or revise it.
The reviewer sees the context before deciding. The workflow waits for their response.
Explore the two outcomes in this example
When the waiting limit expires, the workflow receives a timeout outcome. It does not count as approval.
Free includes browser runs. Build and verify a workflow before organising recurring tasks.
Server runs start on Starter. Plans distinguish total run allowances from server run allowances: compare them against your workload.
See allowancesProfessional, Business and Enterprise include human approval steps. Configure decisions and waiting behaviour for your process.
Tell us about the inputs, decisions and expected result. In the demo, we’ll identify the steps to bring into a workflow.
When a process needs a decision before continuing. At the configured step, the workflow waits for the outcome; subsequent actions such as communications or notifications depend on the chosen path. Approval is one possible part of automation, alongside triggers and actions.
Explore further →