Workflows
Something happens. The workspace acts.
A reply arrives, a deal changes stage, a form is submitted. A condition decides, and the workspace does what you would have done by hand.
A workflow starts from an event, not a schedule. A reply arrives, a deal changes stage, a form is submitted, a meeting ends. Then a condition decides, and the workspace does the thing you would have done by hand.
The canvas
A trigger at the top, then conditions and actions below it, with branches where a condition splits. Click a node to configure it. One plus adds the next. Ask the agent to build or change it, and the canvas redraws while you watch.
Triggers
- Records
- Created, updated, status changed, stage changed, tag applied, owner changed.
- Conversations
- Message received on any channel, reply to a sequence, email opened or clicked.
- Forms and chat
- Form submitted. Website chat started. Ticket created or stale.
- Meetings and calls
- Meeting booked or ended. Call logged with a disposition.
- Money
- Invoice paid or overdue. Subscription changed in Stripe.
- Usage
- A trial activated, or went quiet.
Conditions
Conditions filter which events qualify. Only deals over ten thousand. Only forms from the pricing page. Only people with a persona set. An Ask the Agent step reads the situation and branches on its answer: is this reply positive, is this ticket urgent.
Actions
- Records
- Create or update a person, company or deal. Set a field, a status, a tag, an owner.
- Messages
- Send an email, a text from the business number, a LinkedIn message when the extension is up.
- Sequences and tasks
- Enroll or unenroll. Create a task for someone, due when.
- Notify
- Post to Slack, email a teammate, notify in the app.
- The agent
- Hand the event to the assistant with instructions, and let it act.
- Wait
- Pause for a delay or until a condition is met, then continue.
Runs
Every workflow keeps a run history: what fired, what it did, any error. A noisy trigger cannot double-fire an action. Pause a workflow and its runs stop; resume it and they continue.
Three to start with
- 1Form submitted from the pricing page: create a deal, enroll in the demo sequence, notify #inbound.
- 2Deal moved to Closed Won: mark the company a customer, send the onboarding plan, post to #wins.
- 3Sequence reply with positive intent: create a task for the owner due today, unenroll.
Around workflows
The parts of the workspace this one works with.
Sequences
Multi-step outreach across every channel, with delays, conditions and branches. Build once, enroll many.
A sequence is a series of steps that runs per enrolled person. Email on day zero, LinkedIn connect on day two, and if they accept, a LinkedIn message. If they do not, a follow-up email instead. Build it once. Enroll a person, a list, or everything a filter matches.
Forms
A block-based builder. A submission creates or updates a person and can trigger a workflow.
A form is a page you publish, a link you share or embed, and a submission that becomes a record. A demo request, a waitlist, a survey, a partner inquiry. The submission is a workflow trigger, so what happens next is yours to decide.
The assistant
Your agent, wired into your workspace. Claude, Codex or Cursor’s. It reads what you can read and does what you can do.
The panel is your agent with your workspace in front of it. Claude, Codex or Cursor’s, whichever you connect. It can read records, conversations, meetings and reports, and it can act: create and update records, send and schedule messages, build sequences, run reports, change settings. With your permissions, in your workspace, and nowhere else.
Questions
Can I test a workflow?+
Run it against a record by hand from the builder and read the run.
What if an action fails?+
The run shows the error. Fix the node and retry the run.
Is there a limit on runs?+
No. Runs are logged and kept.
How many sequences can a person be in?+
One at a time by default, so two reps never write on the same day. An admin can allow more.
Can a step send from a different mailbox?+
Yes. A sequence pins a mailbox or a sender group.
What happens at the weekend?+
Steps respect working days and the timezone of the person when it is known.
Can I embed it on my site?+
Yes. A script embed, or an iframe, or just the link.
Spam?+
Submissions are rate-limited and checked. A suspicious one is held rather than made into a person.
Can it send mail without asking?+
It can, with your permissions. Ask it to draft and you review, or let it send and it tells you what went out.
Does it see other people’s data?+
Only what your permission profile allows. A member’s assistant sees a member’s view.
Which agent?+
Whichever you connect: Claude, Codex, or Cursor’s. It runs in the app, or locally through the desktop app when one is awake.
Try workflows on your own data
Connect your email, then open a person. Most of the product shows up on that one page once the mail is in.
More in Agent
An assistant with your permissions, and the workflows, routines and forms that run without you.
It reads what you can read and does what you can do. With your permissions, in your workspace, and nowhere else.
Describe the recurring ask once, then it is one click.
Every Monday at eight, summarise last week’s pipeline and post it.
A block-based builder. A submission creates or updates a person and can trigger a workflow.