Two ways to bring records in
Workspace admin2 min readUpdated 5 Sep 2026
In this article
They grew up for different jobs. A workflow Pull step is for automation with conditions attached; a sync configuration is for plain, repeating reference data.
- Why both exist, and what each is good at
- The two side by side, on five points that matter
- Why you should pick one per table and stick to it
- Which to choose, and whether they conflict
01 · Why
Why are there two?
- A workflow Pull step is for automation with conditions attached: pull, then check something, then flag or notify. It runs on the workflow’s trigger.
- A sync configuration is for plain, repeating reference data: keep this table looking like that list in QuickBooks. It runs on its own.
02 · What it means for you
| What | Workflow Pull step | Sync configuration |
|---|---|---|
| Set up in | Workflows → a workflow | Integrations → a connection |
| Choose fields in | The step's mapping editor | The Field Mapping Wizard |
| Runs when | Its trigger fires, or you press Sync on the table | You press its run icon, or on a schedule |
Enables the table’s Sync button | Yes | No |
| Can pause | Turn the workflow off | Turn off the pull switch |
Both write into the same tables, so if you set up both for the same records they will both keep writing.
03 · FAQ
Common questions
Which should I use?
If you just need a table kept up to date, use a sync configuration — it is far less work. If something has to happen to the records as they arrive, use a workflow.
Can I see all of them in one place?
No. Workflow pulls are in Workflows; sync configurations are behind Sync Mappings on each connection.
Do they conflict?
Not in the sense of erroring. They will each update the record according to their own mapping, so the last one to run wins.