Skip to content

Every workflow step, and what it does

A workflow is one trigger and a chain of steps. This page is the reference for the steps. Press a step’s card on the canvas and its settings open in the drawer on the right; the heading in that drawer links back here.

  • Drag empty grid to move around, with a mouse or a finger. Fit to screen shows the whole workflow at once. A click on empty grid closes the drawer.
  • Copy and Delete sit under each step’s name in the drawer, and on the card when you hover over it or have it open.
  • Deleting a step in a chain takes only that step, and the steps under it move up to take its place. The message that confirms it has Undo. A step with more than one road in use (an If / Else, or a question with steps on its Answer did not fit road) takes the steps on those roads with it, and asks first.
  • After Copy, press any + and pick Paste step. The pasted step keeps its roads and their conditions, with nothing under them yet.
  • Cmd-Z undoes and Cmd-Shift-Z redoes. Cmd-S saves. Delete removes the step you have open, when the canvas has focus.
  • A draft saves itself a few seconds after you stop editing, and Save saves it at once. On a published workflow the button reads Save draft: contacts keep getting the published version until you press Publish again.

Before the list: four limits that apply to all of them

Section titled “Before the list: four limits that apply to all of them”
  • A single run lives for 7 days unless you give the workflow longer, up to 90 days: open the workflow’s menu, then Settings, and change Keep a contact in this workflow for up to. A question nobody answers by then ends the run rather than sitting there.
  • A run sends at most 6 messages in one turn and 30 across its whole life. A chain that tries to send more stops sending, it does not loop.
  • Nothing runs at all until two switches are on: you publish the workflow, and your district admin has turned workflows on for the team. The list page says so when the second one is off.
  • A workflow that names a business runs on that business only. One that names none runs on your own businesses, or on anybody’s when your district admin owns it. Read access to a colleague’s inbox does not count.

When a message a workflow queued is held back

Section titled “When a message a workflow queued is held back”

A workflow’s messages wait a few seconds in a queue before they go. One is held back, and never sent, when:

  • you or a colleague wrote to that lead after it was queued. Your words came first, and an automatic line arriving after them would talk over you.
  • the lead asked not to be contacted.

Handing the chat to a person, or closing it, does not hold a message back on its own. A workflow started by Booked or by a closed chat still sends.

Tags, contact details, statuses and closed chats start workflows whoever changes them: you in the CRM or the Inbox, a colleague, or an AI agent. A change made by hand is picked up within a minute.

Shortcut in the Inbox is the one nothing in the app starts for you by itself. A workflow on that trigger becomes a button in the conversation itself: open a thread in Inbox, press Shortcuts in the header, and pick it. Give the trigger a form and you’re asked those questions first, and your answers are there to use in the steps below, which is how the Shortcut: Escalate This To Me and Shortcut: Log A Call templates are built.

Chat Starts fires on a contact’s first message ever. Switch on Also when they write again after a quiet spell and it fires again when somebody writes after the hours you set with nobody writing either way, or writes into a conversation that was closed. Anybody who opted out is never reopened this way.

Starts a workflow when another app sends details to a web link of your own: a website form, Zapier, Make, or a Lark automation.

To connect one:

  1. Set the trigger to Another App Sends a Contact.
  2. Add a Business condition and pick which of your businesses the contact belongs to.
  3. Press Save, then copy the Web link and the Secret key from the trigger.
  4. In the other app, POST JSON to that web link with the header Authorization: Bearer and your secret key.
  5. Publish the workflow.

The payload needs a phone number, sent as phone. Everything else you send is yours to use in the steps: "budget": "5k" becomes $trigger.budget in a message. A name arrives as name, and source sets what the lead’s source reads as.

A number the app has not seen gets a conversation on that business and a CRM card, the same as somebody who writes in.

Note that 120 calls an hour is the ceiling for one workflow. Nothing runs while the workflow is a draft, or while your district admin has workflows or texting new leads switched off.

Each call starts its own journey, so a form sent twice runs the workflow twice. Run only once for each contact, in More options, stops the second one.

Sends what you write to the contact on WhatsApp.

  • Up to 2,000 characters.
  • Put --- on its own line to split one step into two messages. They go out a few seconds apart, at the pause set for the business, not this step’s.
  • Seconds between split messages, under More options, is the pause before the workflow’s next message. It’s never shorter than 1 second.
  • Switch Type to With a picture or file to attach one. A media message can go out with no words.
  • Send from is the number the message goes out on. The number they last talked to is right for almost every workflow.
  • Add a road for when it cannot be sent, under More options, draws a Could not send road. A run takes it when the message can’t leave: there’s no number on the line, or the number is logged out, offline, warned or blocked. A number paused for heat or warm-up only holds the message, so the run goes down Sent.

Use Add their name or details under the box to put the lead’s own details into the words. Pick from that list rather than typing: a placeholder you spell wrong is sent to the lead exactly as you wrote it.

To say something when a detail is missing, type it in If it's empty, say before you pick. Hi $contact.firstname|"there" greets a lead with no name on their card as “Hi there”.

Sends one of your WhatsApp templates that Meta has approved. On a number connected through Meta, it’s the only message that reaches somebody who hasn’t written to you in 24 hours.

  • Pick it under Template. Each one is listed with its language.
  • {{1}} in its words becomes their first name.
  • On a number not connected through Meta, the same words go as an ordinary message.
  • With no approved template yet, the drawer sends you to Message templates in the Inbox to write one.

Sends a question and then holds the thread open until the contact answers.

  • Kind of answer changes what counts as an answer: Text, Pick from options, Number, Date, Phone, Email, Website link, Rating or Location.
  • Pick from options needs at least 2 options and each one is at most 20 characters, because the options are sent as a list the contact reads on a phone.
  • Show as buttons sends up to 3 options as buttons they tap. With more than 3, the options go as a numbered list instead.
  • Save their answer has On their card and For later steps (to put in messages and checks further down), and you can switch on both. A Pick from options question adds a third, As a tag.
  • Add a road for no reply, under More options, gives the step a No reply road for the contact who never answers. Anything from 1 second up to the workflow’s run limit, 7 days unless you raise it.
  • Every type except Text can refuse an answer: an email that is not an email, a rating that is not 1 to 5, a reply that is none of the options. Switch on Add a road for an answer you cannot read and put something on its Answer did not fit road, usually a line saying you did not catch it and a jump back to the question. Without the road, a contact who answers the wrong way hears nothing back and the workflow stops, so it will not publish until the road is there.

Splits the road by what is true about the contact.

  • Up to 9 paths plus Everyone else. Contacts who match none of them go down Everyone else. Press Add a Path for another.
  • Paths are checked from the top and a contact takes the first one that matches. Use the arrows beside a path’s name to change the order.
  • Every path needs at least one condition or the workflow will not publish. A new path has none: press Add condition.
  • For an answer saved earlier in the workflow, pick Saved answer and choose the answer from the list. Each one is named by the question that saved it.
  • Conditions read contact details, tags, answers saved earlier, the business, the last message either way, and how long it has been since one.
  • contains means whole words, any one of a comma-separated list. yes, keen, sure matches “yes keen” and does not match “yesterday”.
  • For an email this workflow sent, pick Email they got, choose the Send an Email step, then Opened, Clicked or Replied. Put a Wait before the If / Else so they have time to open it. A click or a reply counts as an open.

Sends each person down one path at random, in the shares you set, so you can see which path works better.

  • It starts with Path A and Path B at 50% each. Press Add a path for another, up to 5.
  • Give each path a share from 1% to 99%. The shares have to add up to 100%, or the workflow will not publish. Share evenly splits them for you.
  • Somebody who comes back to this step stays on the path they got the first time.
  • Run history shows how each path did.

AI reads their latest message and sends them down the path whose name fits it best. Use If / Else instead when the choice rests on something you can check, such as a tag or a saved answer.

  • Name each path for what the message is about, like “Asking about price” or “Wants to book a call”. The AI picks by those names alone.
  • It needs at least 2 named paths and takes up to 9. Press Add a Path for another.
  • When no path clearly fits, they go down Everyone else. So does a message the AI hasn’t sorted within 2 minutes.

Holds the contact until somebody on your team says yes or no.

  • Write the question under What the team is approving. It goes wherever Tell the Team sends, with a link to answer it, unless you paste a Lark group’s bot link under Ask in a Lark group.
  • To answer, open the workflow’s menu on the list, then More → Run history, and press Approve or Decline on the run that’s waiting.
  • Three roads leave it: Approved, Declined and No answer.
  • No answer is taken when nobody answers within Wait for an answer: 1 hour, 4 hours, 1 day, 2 days, 3 days, 7 days, or 1 to 3 working days. It’s 1 day to begin with.

Pauses before the next step. Minutes, hours or days.

The run limit is the one to watch: 7 days unless the workflow’s settings say longer, up to 90. A Wait longer than the limit will not publish. Neither will a step the run can only reach after it, such as a 5-day wait after a 3-day one in a 7-day workflow: the builder marks it A workflow stops after 7 days, which is reached before this step runs. For an email sequence over three weeks, set the limit to 21 days or more first.

Checks the clock, and sends contacts down Inside your times or Outside your times.

  • Opening hours takes a row per day with its own open and close time. Monday to Friday, 09:00 to 18:00 to begin with.
  • Dates takes a start and an end date, for a campaign with a closing date.
  • The time zone is Singapore unless you change it.
  • At least one day has to be switched on, or the workflow will not publish.

Puts a named person on the conversation. Hand it to offers four answers:

  • You, the advisor the workflow belongs to.
  • Somebody in your team, then Who to pick them. The list is everybody in your district who has a lead sheet.
  • Share it out across the team, then How to share out: Take turns: whoever has waited longest, or Fewest chats: whoever has the fewest open.
  • Nobody: let it go, which takes the conversation off whoever was holding it and hands it back to automatic replies and AI without alerting anybody.

From this step no AI agent and no automatic reply answers over the person holding it, and your alert number is sent their name. Steps after it still run, messages included.

Whoever it goes to is told directly as well. Their bell rings, and the same message reaches their Telegram and WhatsApp assistant when either is connected, with the lead’s name and the last thing that lead said in it. That person can open and answer that one conversation, even though the lead sheet belongs to a colleague. See Work handed to you for their side of it.

Handing a conversation to the person already holding it changes nothing and tells nobody again.

Sets the contact’s status to New, Replied, Booked, Won or Lost: the five words the Inbox filters by, so the rest of the team sees where the lead stands.

Offers the next few times your Pick a Time page says you are free, and books the one they pick. Your page’s own hours, buffers, notice period and daily cap all apply, the appointment shows in your Pick a Time bookings and on the lead’s card, and they get your usual confirmation email with its cancel and reschedule links.

Pick which booking page, what to say above the times, how many times to offer (3 to 6) and how far ahead to look.

Their card needs an email address, because that is where the confirmation goes. Put an Ask a Question for it, saved to Email, before this step when your leads may not have one.

Two roads leave it. Booked carries on with the time in $var.appointment. Could not book is taken when nothing is free, the card has no email, the time went while they were choosing, or Pick a Time is not connected; the reason is in $var.appointment_problem. Switch on Add a road for nobody answering if you also want a No reply road.

An answer that matches none of the times is asked once more before the step gives up, so “the second one” and “Wed 3pm” both work.

Moves the lead’s card to a column on your Contacts board, for example from New lead to Appointment set. The column is matched by name when the step runs, so a workflow that also runs for a colleague’s leads moves each card on that person’s own board. A board with no column of that name is left alone, and the sheet’s log says so.

This is different from Set Their Status above: the status is the five words the Inbox filters by, and this is the column you drag cards between.

Adds or removes tags. Type them comma separated; tags already in use are offered as you type.

Changes how a value looks, or does a sum with it, and keeps the result for the steps after this one.

  • Value is what to change. It’s usually an answer saved earlier, or a detail on their card such as $contact.Premium.
  • Change it to offers text changes such as Each Word Capitalised and Digits only, money and percentages, a Singapore phone number, dates shown another way or moved by some days, and sums.
  • Keep it as names the result, and later steps use it as $var. plus that name, such as $var.premium_text. Also save to their card writes it onto their card as well.
  • If it can’t read the value, the result stays empty and the workflow carries on. Switch on Add a road for a value it cannot read to send those down Could not read it instead.

Reads their recent messages and saves what they said, such as a budget, a product or a yes or no, to their card or for later steps.

  • What it reads is Their last 20 messages or Only what they write in this workflow.
  • Each row is one detail. Say what to look for, pick a Kind (Pick one, Yes or no or A value) and add What it means if that helps. Pick one needs at least two options.
  • Save each row under Save to their card, under Keep it as for later steps, or both. Press Add a detail for another row, up to 8.
  • Anything they didn’t say stays empty, and a detail somebody already filled in on the card is offered, not replaced.
  • Switch on Needs an answer for a row and the step draws a Nothing found road for when that detail isn’t there.

Writes a value onto the contact’s card. The value can be an answer saved earlier in the workflow: press Add their name or details under the box and pick it.

Writes an internal note on the conversation, stamped with this workflow’s name. The contact never sees it. Use it to tell whoever picks the thread up what the workflow already found out.

Reopens a closed conversation so the thread is back in the Inbox. Nothing to set up.

Closes the conversation. What you write under Note about how it ended goes on the thread as a note stamped with the workflow’s name, so the next person to open it can see why it ended. Reason (optional) goes on the same note, such as Welcome closed it: booked.

Sends the contact back, or forward, to a step you name.

  • At most this many times is between 1 and 10, and defaults to 3. It is what stops a circle running for ever.
  • A jump that goes round a loop with no Ask a Question, Wait or Hand to an AI Agent on the way is refused at publish: the builder says the steps go round in a circle. Something on the circle has to pause for the contact or the clock.

Hands the contact to a second workflow. This workflow ends at this step, so the builder offers no + under it.

The workflow you name has to be published and has to use the Started by Another Workflow trigger. You can send the contact to its beginning or to a step part way down it.

Ends the contact’s place in another workflow. Messages that workflow was about to send them are cancelled.

  • Pick One workflow and choose it under Which workflow, or pick Every other workflow for every other one they’re in right now.
  • You can’t pick the workflow this step is in. To end it here, leave the road under the step empty.
  • They can start those workflows again later.

Hands the conversation to one of your AI agents, which answers from there on.

This workflow ends at this step, so the builder offers no + under it. Use it when the script has taken the lead as far as a script can.

The agent has to be published, and your district’s AI agents switch has to be on, or nothing answers.

Borrows an agent for a single answer, in its knowledge and its voice, and then the workflow carries on to the next step.

Under What it should do this time, say what it should do in this one turn. The brief is required. Leave Wait for their reply afterwards on if the answer is a question.

Use this where a script cannot cover what somebody said, but you still want the rest of your steps to happen. Use Hand to an AI Agent instead when you want to hand the whole conversation over.

Sends one private message from your Facebook page to the person who commented on your post. It goes in Messenger, once per comment and within 7 days of it.

  • It works only when every trigger on the workflow is Someone Comments on Your Post.
  • Write it under Private reply, up to 1,000 characters.
  • Their answer arrives in your page’s inbox, not on WhatsApp, so put your WhatsApp link in the reply.
  • It waits for your team to approve it before it goes.
  • Meta allows one private reply per comment, so a workflow holds one of these steps.
  • Add a road for when it cannot be sent draws a Could not send road.

Sends the contact’s details to another app: a Lark or Slack group, Zapier, Make, or a Google Apps Script.

To send a message to a Lark group:

  1. In Lark, add a custom bot to the group and copy its webhook address.
  2. Paste the address into Web link to send to. It has to start with https://.
  3. Under What to send, press Lark message. It already has the contact’s name and number in it.
  4. Press Send a test. The group gets a message about Test Contact.

The step has two roads. Sent means the other app accepted it, answering with a code in the 200s, within 10 seconds. Anything else takes Did not go through, and the reason goes in your activity log.

An app that wants a key, or a request type other than POST, is set under More options.

Anything you put inside quotes in a JSON body is escaped for you. A first message with quotes or line breaks in it can’t break the body.

Open Save parts of the app's reply to keep the reply code, or a value from a JSON reply, under a short name. The steps under it can put it in a message with Add their name or details, and an If / Else can check it.

Note that Lark answers 200 even when it turns a message down. Send a test shows its reply, which reads "code":0 when the message went through.

One turn makes 5 requests at most, and one conversation sets off 10 a minute across all its workflows, after which a request takes Did not go through. Addresses on a private network and http:// addresses are refused.

Adds a row to one of your Google Sheets, with each value under the column of the same name.

  1. Press Copy script. In your sheet, open Extensions > Apps Script, delete what is there, paste the script and save.
  2. Deploy it: Deploy > New deployment > Web app, Execute as Me, Who has access Anyone. Allow access when Google asks, then copy the Web app URL.
  3. Paste it into Web app link. It ends in /exec. Press Check the link.
  4. Under Fill the columns, give at least one column a value.
  5. Press Add a test row. It adds a row for Test Contact, so delete it from the sheet once you’ve looked.

Sheet tab picks the tab, or the first one if you leave it empty. The script lives in your sheet, and only you can see and change it.

Once the row is in, the run takes Added. If it can’t be added, the log says so and the workflow carries on. Switch on Add a road for when it does not go through to send it down Did not go through instead.

Holds the contact until the next day and time you pick, in Singapore time, so a follow-up lands at 9am on a working day rather than at 3am.

Pick the days under On these days, and the time. If that time today has already gone, it waits for the next day you picked.

Note that a workflow keeps a contact 7 days unless you raise it in Settings, up to 90. One day a week can use all of it, and the builder says so on any step below that could then be missed.

Holds the contact until something about them changes, or until you stop waiting.

  • Under Wait until, add conditions on Contact detail, Tags, Status or Email they got.
  • When they’re true, the contact goes down It happened. It’s checked every few minutes.
  • Give up after takes hours or days, at least 1 hour, and starts at 3 days. Still not true by then, and they go down Time ran out.
  • The wait has to fit inside the workflow’s run limit, 7 days unless you raise it in Settings.
  • For Email they got, clicks count for emails this workflow sent. Links in WhatsApp messages aren’t tracked.

Sends your own words to your team about this contact. The contact is not messaged, and the workflow carries on to the next step.

It goes to the Lark group set in Settings under Where handovers go when the business has one, and to your alert number on WhatsApp when it does not. You can also pick one or the other.

Use Add their name or details to say who it is about.

Adds a task to the list of whoever owns the business, linked to the contact, so opening the task opens the person.

Give it a title, notes if you want them, a due date (No date, In 4 hours, Tomorrow, In 3 days or In a week) and a priority.

Records an activity against the contact for whoever owns the business, the way logging one by hand does, so it reaches the same stats and streaks.

Pick the activity, and add notes if they help.

Note that it carries no points unless you switch Count its points on. The workflow logged it, not you, and points that award themselves make the league table meaningless.

Adds a new card for somebody else, such as a referral the contact gave you. It’s not for the person you’re talking to: they already have a card.

  • Name is required. It’s usually an answer saved earlier, such as $var.referral_name. Phone, Email, Tags and Notes are optional.
  • The card goes in the book of whoever owns the business. Name a Book and a Stage, or leave them empty for the first book and its first stage.
  • The same number twice makes one card, not two.

Note that a Book name that doesn’t exist means no card is made, and a Stage that doesn’t exist leaves the card in the first stage, and the sheet’s log says which. The email is kept only when the book has an email field.

Adds a deal to the contact’s own CRM card, the same as adding one on their record, so it counts in your pipeline.

  • Give it a Deal name, an Amount in S$ and a Stage: Open, Won or Lost. The stage is Open to begin with.
  • The amount takes 2400 or 2.5k, anything from S$0 to S$1,000,000,000.
  • One run never makes the same deal twice.

Note that a contact with no CRM card gets no deal, and the run’s log says so.

Emails the contact in your business’s name. Replies reach your own inbox.

  • To starts as $contact.Email, the address on their card.
  • Subject and Email are both required. Test a second subject sends half your contacts each one, and Run history shows which more people opened. The email holds up to 10,000 characters. A blank line starts a new paragraph, and a web address becomes a link.
  • Look is Plain, which reads like an email you typed, or Designed, which adds a Heading, a Picture link and one Button on a card. Links start with https://.
  • Preview shows it filled in for a sample contact, at a computer’s width or a phone’s. Send a test to me puts it in your own inbox, with [Test] in front of the subject.
  • Open Sender and tracking to change the From name (your business’s name to begin with), where Replies go to (your login email to begin with), the Preview line an inbox shows after the subject, and whether to Count opens and clicks.

Every email ends with an unsubscribe link, and mail apps show their own unsubscribe button for it too. A person who unsubscribes is tagged Email unsubscribed on their card and gets no more email from your workflows. Your WhatsApp messages to them are not affected.

A workflow with a Send an Email step also reaches cards that have an email and no WhatsApp number. That happens when the card lands in its column, when someone tags or edits it, or on a schedule, which is how a monthly newsletter gets to your whole board. Its WhatsApp steps are skipped for that card, the log says so, and Run history marks the card email only.

Nobody tagged Email unsubscribed, marked Do not contact, or on the bounce list is emailed. With no address, or one that isn’t an email, nothing is sent, the sheet’s log says why, and the workflow carries on.

A reply comes to your login email from the app, with their address to answer. It’s noted on their chat too. When the workflow’s settings stop it as They write to you, a reply by email ends their journey. Type your own Replies go to address and replies go straight there instead, so they can’t stop it.

Each email’s numbers are in the workflow’s Run history: how many were sent, opened, clicked and replied to, and how many unsubscribed. Some mail apps open every email by themselves, so clicks are the surer sign.

Tells Meta a lead from your Facebook or Instagram form reached a stage, so your ads find more people like the ones who went on to buy.

  • Event name starts as $contact.stage, which sends their status: new, replied, booked, won or lost.
  • It only works for a lead that came in through a Facebook or Instagram lead form, on a business with a Meta dataset set in its setup.

Note that anything else is skipped with a line in the sheet’s log, and the workflow carries on.