Every workflow has one start. Each time it happens, a new case begins at the first step. Choose it in the first sentence of the sheet.
| Start | A case begins when |
|---|---|
| An email arrives | mail reaches the workflow's forwarding address |
| Someone sends a form | your website's form sends to the workflow's form address |
| A visitor writes in the chat | someone writes in the chat on your website |
| You start it | you or your team start it by hand, for one customer |
| Another workflow | a path in another workflow hands it a case and waits |
| At a set time | the time you chose comes: once, or for each row of a list whose date is near |
An email arrives
Someone sends a form
You start it
Another workflow
At a set time
A case
It walks through the steps, one customer or one date at a time.
An email arrives
Each workflow that starts by email has its own forwarding address at
CoRoid, shown in the workflow's Settings → Email. Forward the mailbox
customers write to (for example support@yourcompany.com) to it: every new
mail starts a case, and an answer in the same thread continues it.
A customer
writes to your support address
Your mailbox
support@acme.example
keeps the mail, as before
The workflow
wf-…@mg.coroid.ai
gets a hidden copy and starts a case
The mail flow rule (Microsoft 365)
- If
- the To header includes your support address
- Do
- add the workflow's forwarding address to Bcc
Replies go out from your support address, and an answer in the thread continues the same case.
Replies go out from your own address, not CoRoid's. Set the reply address in the same panel; the first time you use a domain, add the two DNS records it shows (SPF and DKIM) at your DNS host. Once they are found, every workflow can reply from any address at that domain.
Microsoft 365
Microsoft 365 blocks automatic forwarding to outside addresses, and forwarding a mailbox sends everything it gets. Add a mail flow rule that puts the workflow in a hidden copy instead:
- In the Exchange admin centre, open Mail flow → Rules and choose Add a rule → Create a new rule.
- Under Apply this rule if, choose The message headers… → includes
any of these words. Enter
Toas the header, and the address customers write to as the word. Don't choose The recipient is: when the address is an extra address on a person's mailbox, that rule would copy all of their mail. - Under Do the following, choose Add recipients → to the Bcc box and enter the workflow's forwarding address.
- Finish, then switch the rule on: a new rule starts off.
Mail that names the address only on the Cc line isn't copied; add a second
rule the same way with Cc as the header to include it.
Google Workspace
- Turn the workflow on first: Google confirms the address by sending it an email.
- In Gmail, signed in as the mailbox, open Settings → See all settings → Forwarding and POP/IMAP and choose Add a forwarding address.
- Google's confirmation email arrives as a new case. Open it, copy the code, and close the case.
- Back in Gmail, enter the code, choose Forward a copy of incoming mail to the forwarding address, and keep Gmail's copy in the inbox.
Someone sends a form
A workflow that starts with a form has a form address. Point the form on
your website at it, or paste the ready-made form from the workflow's
Settings. email and message are required; name and subject are kept;
any other field reaches the agent under the message. A hidden field catches
spam robots, and the visitor lands on a page of your own site afterwards.
Replies go out by email, and the customer's answer comes back to the case. A form's sender has not proved their address, so every change and every reply for them waits for a person's yes (see Limits, data and safety).
A visitor writes in the chat
Choose when a message arrives in the website chat, then open the workflow's Settings → Website chat:
- List the sites the chat may run on, such as
https://www.yourshop.com. Other sites cannot show your chat. - Copy the line it gives you and paste it into your site's pages, just
before
</body>. The chat appears as a button in a corner of the page. - Turn the workflow on. Open the chat on its own page tries it without your site.
A conversation is a case: the first message starts it, and the visitor's later messages join it. Answers appear in the chat.
A visitor can prove their email with a six-digit code CoRoid sends them. Once they have, answers follow your steps' approval settings and can come at once, and tools that look up the customer's own account may run. Until then every answer waits for your yes, as for a form, and also goes by email when they gave an address. An answer to a visitor who has left the page goes by email too, so set a reply address on a domain you verified.
The chat is a public entry point, so CoRoid limits it: a visitor can write a few messages a minute and start a few conversations an hour, a message is at most 2,000 characters, and new cases count against the same daily caps as forms and email. Every message is checked like an email; one that tries to give the agent instructions waits for a person.
You start it
Start a case by hand from the workflow's Cases, for one customer: their name, their address and what they need.
Another workflow
A path in one workflow can hand a case to another, and wait until it is done: an onboarding workflow can hand each new employee's laptop to an IT workflow, for example. The other workflow's start is Another workflow.
At a set time
For work that follows the calendar: renewals, inspections, agreements, a weekly summary. Choose At a set time, then:
- how often: every day, every weekday, on days of the week, or once a month (on day 1 to 28);
- at what time, in which time zone;
- what each run starts:
- one case each time, for a check that looks at everything at once;
- a case for each row of a list whose date is near: choose the list, its date column, and how many days before the date the case should start.
Every day at 08:00 (Europe/Stockholm)
A case for each row of Licences 30 days before its Expires
Licences
- Gas safetyExpires
2026-12-01In 13 days: a case starts - ElectricalExpires
2027-03-01In 103 days: not yet - Fleet permitExpires
2026-11-25Its case started last week
For each row, a case starts once for each date, however often the check
runs: a licence that expires on 1 December starts one case 30 days before,
not thirty. When the date in the row changes, the new date gets its own case.
Write the dates year first, such as 2026-12-31; spreadsheets can save them
that way.
A workflow you turn on never runs a time that passed before it was on, and a time missed while CoRoid was not running runs once, not once for each time it passed.