Copy for AI

Event data

Your action texts can carry the client, number, amount or balance of each sale, filled in automatically when they run.

How to write it

Event data is written in double braces with its name: {{cliente}}, {{folio}}, {{total}}. Names are the same in every language. You can combine them with free text:

Call {{cliente}} about {{folio}}: {{total}}

When quote COT-128 from Northwind for 48,500 USD triggers the workflow, that title becomes:

Call Northwind about COT-128: $48,500.00

Insert it without typing

In each action panel, below the text fields, you see Event data. Place the cursor where you want the item and tap its name: Cord inserts the braces for you. Only the data carried by the trigger you chose is shown.

You can also type {{ in the field: Search data opens, with the icon of each item’s type and the value carried by the latest event of that trigger in your account (for example, “Northwind” next to Client), so you recognize each item by what it holds. Pick one and Cord completes the braces. If the trigger hasn’t happened yet, you see the variable instead of the value; data read at run time says so.

It works in: the task title, the email subject and message (to the team or to the client), the WhatsApp variables, the Slack message, the Teams message, the HubSpot note, the message of the POST to a URL, and the void reason. The POST’s destination URL does not accept it.

How it looks when it runs

Data type	How it appears	Example
Text	As is.	Northwind
Number	With thousands separators for your account’s language and up to 2 decimals.	1,250
Amount	With the symbol and decimals of its own currency, in your account’s format. An amount in yen comes out without decimals.	$48,500.00
Option	By its name, in your account’s language.	Approved, Deposit, The client
Yes or no	Yes or No.	Yes
Empty	Nothing appears.

An amount already comes out with its currency symbol. Use {{moneda}} when you want the code on its own, for example “MXN” in a note.

If an item arrives empty, it is inserted empty: “Call {{cliente}}” with a client without a name becomes “Call “. That is why each text should also have fixed words.

Data is inserted as text. If a client’s name or a message contains symbols like <, > or &, they are shown literally and do not alter the formatting of the email, Slack or HubSpot.

Current status: checked at run time

Items marked “checked at run time” (Current quote status and Current invoice status) are not stored with the event: Cord reads them when the step runs. In an email sent after a 5-day wait, {{estado_actual}} shows that day’s status, not the one from 5 days before.

If the item does not exist for the trigger

When publishing, Cord checks every text. If you used data that trigger does not carry, you see:

The variable {{saldo}} does not exist for this event.

It usually happens when changing the trigger of a workflow you already built, or when typing the name by hand with a typo. Fix it or insert it from Event data.

Your business data

These five variables exist on every trigger, because they come from your account (Settings › General), not from the event:

Variable	What it brings
{{negocio}}	Your business name.
{{negocio_correo}}	Your contact email.
{{negocio_telefono}}	Your phone.
{{negocio_moneda}}	Your account’s currency.
{{hoy}}	Today’s date in your time zone, like 2026-09-20.

They are mostly for signing an email to the client without typing your name by hand in every workflow: if the business changes its name or phone, the workflows come out right without being touched.

Full list

Quotes, approvals and quote payments

Item	Name	Type
Number	{{folio}}	Text
Client	{{cliente}}	Text
Total	{{total}}	Amount
Currency	{{moneda}}	Text
Status at the event	{{status}}	Option
Current quote status	{{estado_actual}}	Option, checked at run time
Who caused it	{{actor_tipo}}	Option

Plus, depending on the trigger:

Trigger	Item	Name	Type
A message is posted on a quote	Who wrote it	{{autor}}	Option
A message is posted on a quote	Message	{{mensaje}}	Text
A quote requests internal approval	Reason	{{motivo}}	Text
An internal approval is decided	Decision	{{decision}}	Option
A partial payment arrives	Amount paid	{{monto}}	Amount
A partial payment arrives	Balance due	{{saldo_pendiente}}	Amount
A partial payment arrives	Payment type	{{tipo}}	Option
A partial payment arrives	Plan payment name	{{etiqueta}}	Text
A payment plan milestone is completed	Plan payment name	{{etiqueta}}	Text
A payment plan milestone is completed	Payment amount	{{monto}}	Amount
A payment plan milestone is completed	Due date	{{vence}}	Text
A quote is edited and resent	Previous total	{{total_anterior}}	Amount
A quote is about to expire	Days until it expires	{{dias_para_vencer}}	Number
A quote is about to expire	Expiration date	{{vence}}	Text

A draft is deleted carries everything in the first table except current status.

Cord Invoicing invoices

Applies to issued, sent, paid, payment fails, overdue, about to be due, past due for days, voided and marked uncollectible.

Item	Name	Type
Number	{{numero}}	Text
Client	{{cliente}}	Text
Total	{{total}}	Amount
Balance due	{{saldo}}	Amount
Currency	{{moneda}}	Text
Country	{{pais}}	Text
Status at the event	{{estado}}	Option
Current invoice status	{{estado_actual}}	Option, checked at run time
Who caused it	{{actor_tipo}}	Option

Plus, depending on the trigger:

Trigger	Item	Name	Type
An invoice is about to be due	Days until due	{{dias_para_vencer}}	Number
An invoice is about to be due	Due date	{{vence}}	Text
An invoice has been past due for days	Days past due	{{dias_vencida}}	Number
An invoice has been past due for days	Due date	{{vence}}	Text

“A quote is invoiced” and “A quote CFDI is stamped” use quote data, not these.

Disputes and refunds

Item	Name	Type	Triggers
Quote number	{{folio}}	Text	All
Client	{{cliente}}	Text	All
Disputed amount	{{monto}}	Amount	Disputes
Refunded amount	{{monto}}	Amount	Refunds
Currency	{{moneda}}	Text	All
Reason	{{motivo}}	Text	All
Response deadline	{{fecha_limite}}	Text	Disputes
Outcome	{{estado}}	Option	A dispute is closed
Failure reason	{{motivo_falla}}	Text	A refund fails

Payouts

Item	Name	Type	Triggers
Payout amount	{{monto}}	Amount	Both
Currency	{{moneda}}	Text	Both
Arrival date	{{llegada}}	Text	Both
Failure reason	{{motivo_falla}}	Text	A payout fails

Payments account

Item	Name	Type
Can accept online payments	{{puede_cobrar}}	Yes or no
Can receive payouts	{{puede_depositar}}	Yes or no
Pending verification items	{{pendientes}}	Number
Restriction reason	{{motivo_bloqueo}}	Text

Clients

Item	Name	Type
Company	{{empresa}}	Text
Email	{{email}}	Text
Country	{{country_code}}	Text
Payment terms	{{terminos}}	Option (Due on receipt, Net 7, Net 15, Net 30, Net 45, Net 60 or Net 90)
Who caused it	{{actor_tipo}}	Option

A client is updated also carries the previous value of three items: Previous company {{empresa_anterior}}, Previous email {{email_anterior}} and Previous payment terms {{terminos_anterior}}.

A client is deleted only carries Company and Who caused it.

Products

Item	Name	Type
Name	{{nombre}}	Text
List price	{{precio_lista}}	Amount
Active	{{activo}}	Yes or no
Who caused it	{{actor_tipo}}	Option

A product is updated also carries Previous list price {{precio_lista_anterior}} and Active before {{activo_anterior}}.

A product is deleted only carries Name and Who caused it.

Tasks and promises

Trigger	Data
A task is created, A task is completed	Title {{titulo}}, Who caused it {{actor_tipo}}
A payment promise is recorded	Promised amount {{monto}}, Currency {{moneda}}, Promised date {{fecha_promesa}}, Who caused it {{actor_tipo}}
A payment promise is kept / broken	Promised amount {{monto}}, Currency {{moneda}}, Who caused it {{actor_tipo}}

Scheduled trigger

Item	Name	Type
Date	{{fecha}}	Text
Day of the week	{{dia_semana}}	Text
Day of the month	{{dia_mes}}	Number
Hour	{{hora}}	Number

Next

• Publish, pause and delete
• Actions