Automations
An automation is a short sequence like “when they accept my invitation, wait two working days, then send a thank-you message”. It runs per person, and any reply from the person stops their run, so nobody gets a follow-up after they’ve already answered.
Create one
Section titled “Create one”The easiest way is to ask your assistant:
When someone accepts my invitation, wait two working days and then send: “Thanks for connecting, {{first_name}}. How is the quarter going at {{company}}?” Stop if they reply.
The assistant shows you the steps and creates it with create_automation. You’ll see it under Automations in the dashboard.
How it’s built
Section titled “How it’s built”A trigger, one of:
invitation.accepted: someone accepted an invitation from this account.message.received: someone sent this account a message.
Optionally limited to people first contacted by a specific job (sourceJobId), so an automation only follows up on one campaign.
Up to 10 steps, each one of:
| Step | Settings |
|---|---|
wait |
workingDays (0–30), days (0–30) or hours (0–720) |
send_message |
text, up to 1,900 characters. May use {{first_name}} and {{company}}. |
connect |
Optional note, up to 300 characters. Not available after invitation.accepted (they’re already connected). |
Rules that still apply
Section titled “Rules that still apply”Every message an automation sends is a normal write: it goes through approvals (in approve or assist mode), budgets, working hours and guardrails like the duplicate-text check. Write each step so it reads naturally to the person; the templates fill in their name and company.
Pause, resume, archive
Section titled “Pause, resume, archive”From the dashboard, from your assistant (“pause my thank-you automation”), or the API (POST /v1/automations/{id}/pause, /resume, /archive). Pausing or archiving stops everyone currently waiting in it; resuming applies to new people from then on.
Each automation shows how many people are waiting, completed and stopped (for example because they replied).