Lookups
A step that asks before deciding. It brings a number from your account and leaves it available to the steps that follow.
What it is for
A workflow only knows what the event carried. “Quote COT-7 for 150,000 was approved” says nothing about how much that client owes you or how your receivables are doing, so an alert could not include it and a condition could not decide on it.
A lookup closes that gap: you place it earlier, Cord runs it, and its results become variables for the rest of the workflow.
A lookup only reads. It never changes anything in your account, so you can use it as often as you want.
How to add one
- Click Add a step › Action or lookup.
- In the finder, filter by Lookup or type what you are after (“overdue”, “pipeline”, “balance”).
- Pick the lookup. If it has a days parameter, set it.
- The panel shows Makes available: those are the variables you can use afterwards.
The lookups
| Lookup | What it brings | Variables |
|---|---|---|
| Overdue receivables | How much you are owed past the due date. | {{vencido_total}}, {{vencido_cantidad}}, {{vencido_dias_max}} |
| Open pipeline | How much sits in sent or viewed quotes that are undecided. | {{pipeline_total}}, {{pipeline_cantidad}} |
| What was collected | How much you were paid over the last days you choose (1 to 90): quote payments and invoice payments, minus what was refunded. {{cobrado_cantidad}} counts the payments received. |
{{cobrado_total}}, {{cobrado_cantidad}} |
| What is about to be due | How much is due over the next days you choose (1 to 90). | {{por_vencer_total}}, {{por_vencer_cantidad}} |
| Client balance | How much the event’s client owes and how much is overdue. | {{cliente_saldo}}, {{cliente_vencido}}, {{cliente_documentos}} |
Amounts come out in your business’s currency: what you sold in another currency is converted the same way as in Reports, with the rate frozen on the document or the one published that day, and what was collected is the same figure you see there. If a currency has no rate available at all, its amount is left out of the total; a rate is never made up.
Order matters
A lookup variable exists from the step that brings it onward. If you use it before, the workflow will not publish and the editor says so: “The variable {{vencido_total}} comes from a lookup that runs after this step.”
The same applies inside a branch: what the If met branch looks up does not exist in the If not met branch. If both need it, put the lookup before the condition.
Client balance needs a client
Client balance uses the event’s client, so it only works with triggers that carry one: quotes, invoices, payments and clients. A scheduled or payout trigger has no client to ask about, and the workflow cannot be published with that lookup.
A full example
“Your Monday: collected, overdue and who to call”, one of the ideas Cord ships with:
- When this happens: every Monday at 9.
- Lookup: what was collected in the last 7 days.
- Lookup: overdue receivables.
- Lookup: the open pipeline.
- Action: alert the account owner, with the subject “Your week in Cord (
{{fecha}})” and the message “Collected in the last 7 days:{{cobrado_total}}across{{cobrado_cantidad}}payments. Overdue:{{vencido_total}}across{{vencido_cantidad}}documents, the oldest{{vencido_dias_max}}days past due. Left to close:{{pipeline_total}}across{{pipeline_cantidad}}quotes.” With Slack or Teams connected, the alert goes out there.
You can extend it: add the lookup for what is about to be due, or change the recipient to the whole team.
Limits
Each lookup is a step, so it counts toward the 30-step maximum per workflow. They have no hourly cap of their own: they only read.