The Deliver Data step lets you send data from your workflow back to your connected systems—cleanly, accurately, and with full control. This guide walks you through how to use the step effectively, including how to manage field mappings manually or automatically.
Note: This step is commonly used alongside the Activate Data step, which identifies the records you want to act on.
Step 1: Open the Deliver Data Step
Once you've added the Deliver Data step to your workflow, click into it to begin setup.
Step 2: Understand Auto-Mapping
When you open the step for the first time, the system will automatically map fields between your workflow and the destination dataset. A pop-up will confirm that this happened.
Auto-mapping uses how fields were used earlier in the workflow to make smart guesses about what should connect.
Step 3: View & Edit Field Mappings
You can now see all the field mappings directly in the Deliver Data step.
Here’s what you can do:
- Add a new mapping: Click “Add Mapping” to manually pair fields.
- Remove a mapping: Click the "X" next to a row to delete it.
- Clear all mappings: Start over with a clean slate.
- Run auto-mapping again: Useful if you’ve updated earlier steps and want to refresh the mappings.
Re-running auto-mapping will overwrite any manual changes you’ve made, so you’ll be asked to confirm before proceeding.
Step 4: Customize It Your Way
With full control over mappings, you can:
- Adjust field pairings if your destination system changed
- Fine-tune data delivery based on business logic
- Ensure accurate alignment with external systems like Salesforce or data lakes
Summary
The Deliver Data step gives you a clear and flexible way to deliver workflow data. With both automatic and manual mapping options, you stay in control while saving time.
Key benefits:
- See and edit mappings directly
- Use smart auto-mapping when needed
- Make last-mile changes before data is delivered
For best results, use this step together with the Activate Data step to define and act on the right records.
Comments
0 comments
Article is closed for comments.