Mapping in Zapier controls how information from your trigger step is passed into your Access PaySuite DDCMS action. When you test a trigger, Zapier loads a sample record so you can choose the fields you want to use, such as customer details, payment information or Direct Debit values.
Mapping fields in your Zap
When you select an action, Zapier displays the fields required by Access PaySuite DDCMS. You then choose which trigger fields should populate each one. Required fields must be mapped before the Zap can run. Optional fields can be left blank if they're not needed for your workflow.
Mapping guidance
To ensure consistent and reliable automations:
Use the CustomerReference from your trigger wherever possible.
Enter dates in the format YYYY‑MM‑DD.
Use plain numbers for amounts, without currency symbols or commas.
Combine static text with trigger fields if needed, for example:
DD-{{CustomerReference}}.Avoid hard‑coded values unless they apply to every scenario.
Test your mapping
Before turning your Zap on:
Run Test Action.
Check that all required fields contain data.
Confirm that references or IDs are mapped correctly.
Review the output to ensure the action creates or updates the expected record.
Testing helps prevent errors and ensures your automation works correctly with your own Access PaySuite DDCMS data.
📌Note: Zapier only displays fields found in the sample record you load during trigger testing. Custom fields created in Access PaySuite DDCMS aren't available for mapping, as they're not included in Zapier’s sample data.