Best practices
There are a few recommendations that will make your workflows more reliable and easier to maintain.
Always test your triggers.
Testing ensures Zapier can load sample data, which makes mapping easier and prevents errors later.Name your Zaps clearly.
Clear names help with maintenance and make it easier for teams to understand what each Zap does.Use filters and paths when appropriate.
These help you control when your automation runs, such as only continuing for failed payments or specific recurring updates.Separate sandbox and production.
Add each connection separately and label them clearly so they are not mixed up.
FAQs
Can a Zap have more than one trigger?
No. Each Zap can only have one trigger, although you can add as many actions as you need.
Can I connect both sandbox and production?
Yes. Connect each environment separately in Zapier and give each connection a clear name.
Is Zapier secure?
Yes. Zapier uses OAuth‑based authentication and encrypts stored credentials.
Troubleshooting
No sample data appears
Create a new customer/payment in Access PaySuite DDCMS, try Load More, and check the correct environment is selected.Action validation errors
Make sure required fields are filled, dates use YYYY‑MM‑DD, and amounts are numbers only.Duplicate entries
Add a Zapier Filter step so only the records you want are synced.