Help centre
Setup guide · step 31 of 52 · stage 7, Automate the follow-up

Automations

Build a rule that watches for something, then does the work: an activity, an email or text, a field update, a webhook, or a wait until someone replies.

An automation is a rule you build once: When something happens, If the record matches, Then do these steps. Go to Settings › Automations.

Automations need Growth or Pro. Growth includes up to 30 active automations; Pro is unlimited. The free trial runs as Pro, so you can try them all. See what each plan includes.

The quickest start is Start from a recipe. The gallery has ready-made automations — round-robin a new lead and call them within the hour, escalate a lead nobody has touched in 24 hours, run a checklist when an opportunity reaches Proposal, kick off onboarding when it's won, send signed sales orders to operations, tell finance about a confirmed order, follow up a declined order, and nudge quiet opportunities. Open one, change the names and times to suit you, and save.

1 When: the trigger

One trigger starts the automation, and it decides which record the rest of the rule works on — an opportunity, a lead or a contact.

Opportunities: created · enters a stage (any stage, or one you pick) · won · lost · updated (any change to value, owner, close date, forecast category or a custom field) · a tag is added (any tag, or one you name) · no activity for a number of days.

Leads: created · a tag is added · untouched for a number of hours (open leads with nothing logged since they arrived).

Contacts: created.

Sales orders (conditions and actions use the order's opportunity): confirmed · customer signs · customer declines to sign · handed over · fulfilled.

Activities: an activity is completed on an opportunity, of any type or one you pick.

Dates: a date on an opportunity or a contact is reached. See Date automations below.

Changing the trigger to a different type of record clears the conditions and resets any steps that pointed at the old record's fields.

2 If: conditions (optional)

Conditions narrow which records the automation acts on, and they are checked once, when the run starts. Build them from any field on that record, including your custom fields, with up to 20 conditions in a set. All of them must be true — there is no "any of these" at this level.

For opportunities you can test the title, value, status, stage, owner, contact, organisation, expected close date, tags, days in the current stage, won or lost date and when it was created. Leads add source and priority. Contacts have name, email, phone, job title, organisation, owner and how many open opportunities they have.

3 Then: the steps

Step 3 has two views, and you can switch between them at any time with the Flow and List buttons. Flow is the default: the trigger sits at the top as a When card, each step is a card below it joined by a line, and the path finishes with End. Click a card's header to open it and fill in its settings. The arrow buttons move a step up or down, and the + button between any two cards adds a step there. List is the older stacked editor and does exactly the same job.

An automation can have up to 10 steps on a path and 30 steps in total.

Splitting the path

The last item in the + menu is If / otherwise (split into two paths). It gives you a Yes column and an Otherwise (optional) column, and the two paths rejoin afterwards. Unlike step 2, this condition is checked when the run reaches that step, using the record as it is then — so it's the right tool for "by now, has the value gone over $20,000?". You can nest a split two levels deep.

The steps you can use

  • Wait before the next step — an amount of seconds, minutes, hours, days, weeks or months. For days, weeks and months you can also wait until a set time of day. Waits are checked every five minutes, so expect anything shorter than that to happen within about five minutes of the time you set. A wait must have a step after it on every path, and the waits down any one path can add up to at most 365 days.
  • Wait until the record matches — carry on as soon as any of these happens: the record matches a set of conditions (the conditions within that set must all be true), the contact replies to an email, or the contact opens an email sent after this run started. Set a time limit with Give up after, and choose whether to carry on anyway or stop the automation when it runs out. If the thing you're waiting for has already happened when the run reaches this step, it carries straight on without waiting.
  • Create an activity — a call, meeting, task, deadline, email or lunch, with a subject, a due time in hours, and either the record's owner or a named person.
  • Send an in-app notification — to the record's owner, all admins, or up to 20 named people.
  • Assign owner (round robin) — rotates through the people you choose, in order.
  • Update a field — on an opportunity: owner, stage, forecast category or the expected close date set a number of days from now. On a lead: owner or priority. On a contact: owner. Plus any of your own fields, except calculated ones.
  • Add tags and Remove tags — up to 10 at a time. New names join your tag library; tags the record doesn't have are ignored. See Tags.
  • Add a note, optionally pinned.
  • Send a survey to the contact — emails one of your surveys that is set to "When an automation sends it". Make it in Surveys first. See Satisfaction surveys.
  • Send an email to the contact — either a saved template or an email you write in the automation itself, with a subject and message. See the warning below about which mailbox it comes from.
  • Email the sales order PDF — to the opportunity's owner, the customer contact, or named people. Once an order is signed, the signed copy and certificate go with it.
  • Send a text message to the contact — up to 500 characters, sent to their mobile through your own SMS provider. Pro includes texts; on Growth they're an add-on. See Text messages.
  • Call a webhook — ZyfrHub POSTs the record's details as JSON to an address you give. See Webhooks below.
  • Post to Slack / Teams — up to 500 characters, to the channel connected in Settings › Team alerts & TV, with a link to the record.
  • Update the sales order status — to handed over or fulfilled.

In any text you can use merge fields: {{record.title}}, {{record.value}}, {{owner.name}}, {{contact.name}}, {{organization.name}}, {{stage.name}}, and for orders {{order.number}}, {{order.total}} and {{order.link}}. If a merge field has no value, the step is skipped and the reason is logged rather than sending something half-finished.

Emails sent by an automation

Two things about automated email catch people out, so they're worth saying plainly:

  • It sends immediately. An email you write in the automation is not a draft and there is no approval step. If you want to review before sending, use a Create an activity step instead and write the email yourself. (The separate AI draft replies add-on is the one that drafts and waits for you — it isn't part of automations.)
  • It comes from the mailbox of whoever built the automation, not the record's owner, and goes to the contact's first email address. If that person leaves the workspace or disconnects their mailbox, every run of that automation fails. If you build automations for the team, use an account that will stay.

Webhooks

Give the step an address and ZyfrHub POSTs JSON with the record's type, id, title, value, currency, stage, owner, contact, organisation and a link to it, plus the automation's name.

  • The address must start with https:// and be a public internet address. A private, internal or cloud-metadata address is rejected when you save and again when the automation runs, so you can't point it at a machine on your own network.
  • Redirects are never followed, the request times out after 10 seconds, and there's no signing secret — the receiving end can't verify it came from you, so don't send a webhook anywhere you wouldn't accept anonymous data.
  • Anything other than a 2xx answer marks the run as failed.

Slack and Teams

An owner or admin first connects the channel in Settings › Team alerts & TV by pasting an incoming webhook link — Slack's starts with https://hooks.slack.com/, and Teams uses a Teams Workflows webhook. There's no app to install. Until one is connected, a Post to Slack / Teams step fails rather than being quietly skipped.

Date automations

Pick A date on an opportunity is reached or A date on a contact is reached, then set the row that reads N days before or after [date] at [time].

The dates you can use are the expected close date, a sent quote's valid-until date, a subscription renewal date, the due date of an open activity, and any date field you've added yourself. Offsets go up to 365 days either side, and the time is a whole hour in your workspace's time zone.

  • It runs once per date. If you change the date, it can run again for the new one.
  • Only open opportunities are considered, except the renewal date, which follows the subscription.
  • A date already in the past isn't acted on, and a date whose moment passed more than six hours ago is skipped — so back-dated dates never fire, and a long outage means that day's date runs are missed rather than all arriving at once.

Who can create automations

  • Owners and admins can create, edit, pause and delete every automation.
  • Team managers can create automations, and change only the ones they created.
  • Anyone else needs switching on individually. Owners and admins do that in the Who can create automations section on the Automations page, which lists everyone with a tick box. Owners, admins and team managers show as Always.

Everyone else can see the automations list but not create anything.

One important limit: an automation built by a team manager or an allowed member only acts on records that person can see under your record-visibility settings. Records outside their view are skipped silently — no run, no error — which can look like the automation isn't firing at all. If an automation needs to act across the whole workspace, an owner or admin should build it.

Watching them run

  • Recent runs lists when it ran, which automation, which record and the result: success, waiting, failed, stopped or cancelled. Open a row for the detail of each step.
  • An automation that fails never blocks the change that triggered it. The failure lands on the run, not on your work.
  • Switching an automation off cancels its waiting runs.
  • Editing an automation doesn't re-route runs that are already waiting — they finish the steps as they were when they started. The card shows an amber note when that's the case.
  • A tick box above the list, for owners and admins, stops waiting runs on their own when the opportunity is won or lost, the lead is closed, or the contact replies. It's on by default and applies to every automation with a wait. The exception is a step that is explicitly waiting for a reply: that one isn't cut short by the reply it was waiting for.
  • On a plan without automations your rules stay saved but don't run, and waiting runs stay paused rather than being thrown away. Pausing an automation is always allowed, even then.

If something doesn't work

  • A text message step failed. Either the plan doesn't include texts (Pro, or Growth with the add-on), the contact has no mobile, or they haven't agreed to texts yet. The step is offered on any plan with automations but only checked when it runs.
  • An email step failed. Check the creator is still in the workspace and their mailbox is still connected.
  • A Slack or Teams step failed. Check the webhook in Settings › Team alerts & TV still works.
  • A "wait until" didn't wait. The record already matched when the run reached that step, so it carried straight on. The run detail says already met.
  • Nothing is firing and there are no runs at all. If the automation was built by a manager or a member, the records are probably outside what they can see.
Still stuck? In ZyfrHub, click ? in the top bar, then Contact support, or email support@zyfrhub.com.
New to ZyfrHub?
14 days of the full Pro plan, no card needed.