Follow-up on every sale, on autopilot.

"When this happens, do this" rules that take the next step for you: a task when the client opens the quote, a reminder before the invoice is due, a Slack message when the deposit lands. No code.

Start for freeSee a real quote

Starting on the Free plan: 1 active workflow on Free, 5 on Starter and no cap from Professional. Runs are unlimited

Quote follow-up ladder
143 runs · 30 days● Active
When this happens
A quote is sentquote.sent
Do this
Wait until the client opens or approvesDeadline: 2 days
If it happens
Create a taskCall {{client}} about {{folio}}
Slack
Send a Slack message#ventas
If the deadline passes
Email the clientAny questions about {{folio}}?
WhatsApp
Send the client a WhatsAppApproved template
Last run 12:36 · COT-0148 · completed0 errors

WHEN THIS HAPPENS

A real event starts the flow, not a reminder in your calendar.

A workflow watches your account. When the client opens a quote, a deposit arrives, an invoice falls due or a chargeback is opened, it runs on its own. It can also run at a fixed time —"every Monday at 9"— read in your business time zone, not the server's.

  • 44 events across quotes, payments, invoices, clients, products and tasks
  • A fixed schedule in your account time zone
  • Time signals: quote expiring, invoice due soon and invoice past due
Choose the trigger44 events
invoice
An invoice is due sooninvoice.due_soon
Time
An invoice is past dueinvoice.past_due
Time
An invoice is paidinvoice.paid
Payments
Every Monday at 9:00Schedule · America/Mexico_City
Schedule
One trigger per workflowYour time zone

DO THIS

Eleven actions, from a task to a HubSpot note.

Create a task for the right person, email the team, write to the client with your brand or send them a WhatsApp with your approved template. Post to Slack or Teams, add a note in HubSpot or send the data to your own URL. On the document itself it only does what is bounded: expire an out-of-date quote, approve an internal request or void an invoice with no payments.

  • Email and WhatsApp go to the document's client, never to a typed-in address
  • Slack, Microsoft Teams and HubSpot from the same editor
  • Event data sent to your own URL over HTTPS
Add an action11 actions
Create a taskFor the right person, with a due date
Send a Slack messageYour own text with event data
Send a Teams messageA card in your channel
Add a note in HubSpotOn the client's company
Send the client a WhatsAppWith your approved template
RecipientAlways the document's client

CONDITIONS, WAITS AND LOOKUPS

Wait for the client to decide. And if they don't, follow up.

Split the flow into two branches based on the event data, wait 1 to 30 days or until something happens with a deadline, and look up a figure from your account —overdue receivables, open pipeline, client balance— before deciding. Before publishing, test the draft against the latest real event: lookups run, actions don't.

  • "If met / if not met" branches, no formulas
  • Conditional wait: until the client opens or approves, with a deadline
  • Test without publishing against the latest real event
Test against the latest eventDraft
Lookup · client balance$134,880.00
Condition · balance > $100,000Met
Wait until paid · 5 daysWould wait
Email the ownerNot sent
Lookups run, actions don'tCOT-0148

WHY IT MATTERS

This is what cord workflows actually changes.

Run · COT-0152 · Grupo NorteWaiting
StepResultWhen
A quote is sent
TriggerMon 10:41
Wait until opened · 2 days
Deadline passedWed 10:41
Email the client
DeliveredWed 10:41
Wait for the decision · 5 days
In progressuntil Mon
Each quote runs its own copyQuote follow-up ladder
Staged collection · A-001052Due in 3 days
StepChannelDay
Friendly reminder
Email−3
Due today, with payment link
WhatsApp0
Alert the owner with the balance
Slack+7
It stops by itself when the invoice is paidA condition checks the balance before every step
Days counted inYour time zone
Workflow health · 30 days98.6% completed
CauseWorkflowRuns
Completed
All412
Client phone without country code
Due-date reminder4
Slack is not connected
Monday summary2
Failures grouped by causeNot by message

FREQUENTLY ASKED QUESTIONS

Most common questions about cord workflows.

No. The editor reads top to bottom in two blocks, "When this happens" and "Do this", and every step is picked from a list. Cord also ships 9 ready-to-use ideas —such as the quote follow-up ladder or the staged collection of an overdue invoice— that you can publish as they are or adapt.

Any of Cord's 44 events —quotes sent, viewed, approved or paid; deposits and failed payments; invoices issued, due soon or past due; chargebacks, refunds and payouts; clients, products and tasks— or a fixed schedule such as "every Monday at 9" in your business time zone. Each workflow has exactly one trigger.

No. A workflow does not charge, does not issue invoices or CFDI, does not record payments and does not approve or reject a quote on your client's behalf: those decisions stay with a person or the client. What it does on your documents is bounded and explicit: write to the document's client, expire a quote that is past its validity, approve an internal approval request and void an invoice that has no payments yet.

The Free plan allows 1 active workflow, Starter 5 and from Professional there is no cap. Only active ones count: drafts and paused workflows take no slot. Runs are unlimited too; an active workflow runs every time its event happens.

They finish with the version they started with. What you edit is a draft, and what runs only changes when you press Publish; every new run takes a copy of the version published at that moment.

No. A workflow is never triggered by the events it causes, and a chain of workflows triggering each other is cut after three levels.

Actions post to Slack and Microsoft Teams, add notes in HubSpot and send WhatsApp messages with your WhatsApp Business account. To take Cord events to any other app there are Zapier, Make and n8n, or an action that sends the data to your own URL.

Explore the rest of the product.

Live trackingNo more asking "did you review it yet?".
AI CollectionsAn artificial intelligence agent follows up on every overdue invoice for you: it emails the client, negotiates an installment plan, and only alerts you when it needs your approval.
Cord InvoicingCord issues the invoice, gives it your own numbering, stamps it where stamping is required, sends it to your client with its own payment link, and tells you how much is still owed.
DocumentationStep-by-step guides for cord workflows.

START TODAY

Let the next step take itself.

Publish your first workflow from one of the 9 ready ideas. Free to start.

Start for free

No credit card required · Free plan forever