Zap templates give you a quick, easy way to automate processes in Access PaySuite DDCMS. Each template comes with a ready‑made workflow where the trigger, action, and essential field mappings are already set up for you. All you need to do is connect your accounts and run the automation using your own data.

To ensure templates work reliably across many different environments, they use clean, generic sample data rather than anything tied to a single organisation’s setup. This makes it easy for you to activate an automation immediately or tailor it to suit your own needs.

Build the trigger and action

Set up the trigger and action as you would when creating a standard automation. Zap templates depend on sample data, so choose a trigger that provides consistent information for Zapier to load.

If no sample data appears, create a test customer, payment, or Direct Debit in your Access PaySuite DDCMS Sandbox, then refresh the trigger until a sample record becomes available.

Once the sample loads, choose the action that demonstrates the intended workflow. Typical Access PaySuite DDCMS actions include:

Creating or updating a customer
Creating or amending a Direct Debit
Recording a payment
Passing customer or payment data to another system

After selecting the action, map the relevant fields using the trigger’s sample data.

Mapping guidance

Zap templates are used across many environments, so mappings must remain flexible and avoid anything specific to a single organisation. Hard‑coded IDs, internal references, or formatting unique to one account should not be used.

Reliable, environment‑neutral mappings include:

Customer Reference → CustomerReference
Direct Debit Reference → DD {{CustomerReference}}
Start Date → DateCreated (YYYY‑MM‑DD format)

Using stable, universal fields helps ensure the template works effectively for you and anyone else who uses it.

Optional additions

Most templates only require a trigger and one action. Additional steps can be included if they provide clear value, such as:

A Filter to restrict when the workflow runs
An additional action to notify another system or update a record

📌Note: Zap templates cannot include Code, Webhooks, Formatter, Paths, or Looping.

Title and description

A clear, action‑focused title helps you quickly understand what the automation does. Titles should start with a verb, use the present tense, and follow correct app naming conventions.

Your description should be short, usually two to four sentences, and explain what the automation accomplishes, when it runs, and why it is useful. Keep the language straightforward and use Access PaySuite DDCMS terminology consistently. If you need to adjust anything for your own setup, include a short note at the end.

📌Note: Update the filter conditions if your account uses custom payment statuses.