Platform/Automation

Move work forward.
On your terms.

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.

Workflow: message, note and notification
Workflow: message, note and notification
Workflow: message, note and notification

Workflow configured with native blocks: message, CRM note and notification. Demo not executed.

Your process takes action.

Send the right message

Connect a contact and content to a send block. The channel, account and allowances depend on your configuration and plan.

Record the next step

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 recaps

Notify when it matters

Use workflow conditions to decide when to notify. Push notifications reach enabled workspace colleagues according to the process configuration.

With Agatha

Prepare the next step 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
An example request
“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.

From one list to a view of the group.

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.

Follow-up after an event
  • To contact
  • Awaiting a reply
  • Ready for a conversation
An example of how to organise a campaign.

One list. The whole process in view.

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.

  • Members and progress in one view.
  • Communication and automation outcomes.
  • Direct paths to activities and the monitoring desk.
List overview
List overview
List overview

Native Fiera Milano 2026 list overview · ten fictional contacts and sample stages; no messages sent.

From a contact list to a message to send.

Work with contact lists and prepare communications in the same platform. Email, WhatsApp and Telegram are available according to your plan and connected accounts.

  • CRM lists as the starting point for activities.
  • Messages and recipients in one environment.
  • Channel configuration and explicit allowances.
Start with a CRM listContacts met at the trade fair
The next step after the trade fair
ToSara Galli <[email protected]>

Hello Sara,

Thank you for our conversation at the trade fair. We have prepared a proposal to connect sales and customer data and view the results in one dashboard.

Could we arrange a meeting to review it together?

Prepare the send to your list
Track the outcomes available for the channel
Sample content and fictional recipient · no communication sent.

Before sending, you have the final say.

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.

  • A request with a title and context.
  • Configurable approvers and deadline.
  • Approvals available from Professional.
The proposal is ready
A decision is needed

Can we send Sara the proposal?

The reviewer sees the context before deciding. The workflow waits for their response.

Subject
Dashboard and sales follow-up
Waiting limit
2 days

Explore the two outcomes in this example

If approvedThe workflow continues to the send step.
If rejectedThe workflow follows the revision branch.

When the waiting limit expires, the workflow receives a timeout outcome. It does not count as approval.

Example of a configurable process · no message is sent.

Choose the capacity your process needs.

Try the workflow

Free includes browser runs. Build and verify a workflow before organising recurring tasks.

Run on the server

Server runs start on Starter. Plans distinguish total run allowances from server run allowances: compare them against your workload.

See allowances

Add approvals

Professional, Business and Enterprise include human approval steps. Configure decisions and waiting behaviour for your process.

Which task are you still repeating by hand?

Tell us about the inputs, decisions and expected result. In the demo, we’ll identify the steps to bring into a workflow.

In practice

When does a workflow need approval?

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 →