LoopfourReshape data between systems
Map fields from one system to the format another expects, such as turning a CRM deal into the fields an invoice in your ledger needs.
Systems name the same facts differently. Your CRM may call it "amount" and "company", while your ledger wants "total" and "customer". A transform step sits between them and reshapes a list of records from one form into the other.
- StepList open invoices
- StepTransform: keepOnly invoices with more than $1,000 due.
- StepTransform: mapKeep invoice number, customer email and amount due.
- OutputReminders sent
Before you start
Know which earlier step returns the list and what the next system needs. Ask your developer for calculations or date changes.
What it can do
A transform step works on a list, such as a list of invoices or deals. It does one of two things:
- Pick and rename fields. Each record keeps only the fields you name, under the names you choose. For example, the CRM's company field becomes "customer".
- Keep only some records. Records pass one simple test, such as amount due more than 1000, or status is "open".
It does not do arithmetic, dates or totals. For work such as a due date 30 days after a close date, or a total of all lines, your developer uses a Code step instead.
When you need one
Often you do not. Most system steps let you fill each setting straight from an earlier step's result. See Use results from earlier steps.
Add a transform step
Describe it to chat
The way a transform is set up is not shown as plain settings in the editor. Ask chat instead, for example: "after listing invoices, add a step that keeps only invoices with more than 1000 due" or "map each deal to customer, amount and close date".
Point the next step at its result
In the next step, use the transform step's result, the new list.
Check it worked
Run the workflow with test records. Open the run under Runs, choose the transform step, and compare its Input and Output tabs. Check a few records by hand, the way you would tick a schedule. An empty result can mean no records passed the filter. An unchanged result can mean they all passed. If either is unexpected, ask chat or your developer to check the settings.
If something goes wrong
If the result is unexpected, compare a sample record with the mapping or filter you requested. Ask chat or your developer to correct the settings. For a failed step, see Error messages explained.
Related
Wait before continuing
Pause a workflow for a short, set time before the next step runs, and learn when a schedule is the better way to wait hours or days.
Read, extract and classify with AI
Learn what the AI Agent step does, such as pulling fields from a document or sorting items, and how to check its output before it is used.