ESEN

Cord Workflows

“When this happens, do this” rules that take the next step for you after every sale, without writing code.

What a workflow is

A workflow is a rule that watches your Cord account. When a specific event happens (a client opens a quote, a deposit arrives, an invoice becomes overdue, a dispute is opened), the workflow runs the steps you defined, in order: create a task, email your team, post to Slack or add a note in HubSpot.

The point is that follow-up does not depend on someone remembering. If your team checks by hand which quotes nobody opened, who paid the deposit or which invoices are overdue, a workflow does it for you and leaves the task ready for the right person.

Where to find it

Open Workflows in the app sidebar. The list shows each workflow as a card with its name, the event that starts it, its status (Draft, Active or Paused), how many times it ran in the last 30 days and how many of those runs failed. At the top you see how many active workflows you have against your plan limit.

Cord Workflows is for admins. You need the Settings permission to view, create, edit or publish workflows. People without it see “Cord Workflows is for admins” and can ask the account owner for access.

The pieces of a workflow

Each workflow reads top to bottom in the editor, in two blocks: When this happens and Do this.

Piece What it does Guide
Trigger The event that starts the workflow. There are 41, grouped into quotes, approvals, payments, invoices, clients, products, and tasks and promises. Each workflow has exactly one. Triggers
Action Something Cord does for you: create a task, email the team, send a Slack message or add a note in HubSpot. Actions
Condition Splits the flow into two branches, If the condition is met and If the condition isn’t met, based on the event data. Conditions
Wait Pauses the flow for 1 to 30 days and then continues with the next step. Waits
Event data Values like {{cliente}}, {{folio}} or {{total}} that you can put in your texts and that are filled in when the workflow runs. Event data

A complete example

“Follow up if the client does not open” is one of the ideas Cord ships with. It reads like this:

  1. When this happens: a quote is sent.
  2. Wait 3 days.
  3. Condition: the current quote status is Sent (the client has not opened it yet).
  4. If met: create the task “Call {{cliente}} about {{folio}}” due today.
  5. If not met: do nothing; the client already opened it.

Every quote you send starts its own run of this workflow. Three days later, each run checks its own quote and decides separately.

Draft, published version and runs

  • Draft: what you edit. Change it as often as you like without affecting anything.
  • Published version: what runs. It only changes when you click Publish or Publish changes.
  • Run: every time the event happens, Cord creates a run with a copy of the version published at that moment. If you publish changes later, runs already in progress finish with the version they started with.

All of this is explained in Publish, pause and delete and Runs and errors.

What a workflow never does

A workflow works for your team; it does not talk to your client. It never writes to the client, never charges, never issues or voids invoices, never marks payments and never changes a quote’s status. Those decisions stay with a person. Emails from the “Email the team” action only reach members of your organization.

It also cannot create infinite loops: a workflow is never triggered by the events it causes itself, and a chain of workflows triggering each other stops after three levels. Details in Limits.

Cord Workflows guides