Resources · Zapier integration

Access PaySuite - Direct Debit Zapier integrationAutomate Access PaySuite - Direct Debit with Zapier.

Access PaySuite - Direct Debit Zapier integration: 11 triggers, all instant, and 10 actions to run UK direct debit contracts, customers and payments without retyping them. No search step. Below, what each operation does, what it costs and where it trips.

Beta app Zapier still marks this integration as beta.

See the 21 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Access PaySuite - Direct Debit Zapier integration really does

It links your Access PaySuite account, a UK system for collecting payments by direct debit, to your other tools through Zapier. Zapier runs Zaps: automations made of one trigger, the event that starts things, followed by one or more actions, the steps that do the work. Here a contract, customer or payment event starts the Zap, and the Zap can create contracts and payments, move collection dates or edit a customer.

A first collection set up on its own. Customer Created starts the Zap, Create Contract opens the agreement, Create New Payment schedules the first charge. Nobody copies a payer from one screen to another.

A failed payment that reaches credit control. Payment Failed hands the event to a Zap that posts it in the tool your finance team already reads, so someone can call the payer while the problem is still fresh.

A price change that follows the CRM. Customer Amended starts the Zap and Update Contract Amount adjusts what the contract collects, with the mandatory Comment saying why.

What Zapier does not do here. The app has no search step, so a Zap cannot look up an existing contract or customer by name: the ID has to come from an earlier step, or be typed. No action deletes anything, and Cancel Contract, by its own description, does not stop payment creation. On the bright side, all 11 triggers are instant, so a free plan reacts as fast as a paid one: the polling interval never applies to this app.

To weigh Zapier against other tools for the same job, the n8n vs Zapier and Make vs Zapier comparisons set the criteria side by side.

Vocabulary

Zapier vocabulary in one minute

Eight words carry the rest of this page. Each one in plain terms, once.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it: here, a contract, customer or payment event.
Action
What the Zap does once it has started: the step that writes, sends or changes something for you, such as a new payment.
Task
The unit Zapier bills: one action your Zap completes successfully. The number printed on your plan counts these and nothing else.
Instant trigger
A trigger the app reports itself, calling Zapier the moment the event happens. The editor marks it with a lightning bolt.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. None of this app's triggers work that way.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
Connection
Your Access PaySuite account linked to Zapier once, then offered again to every step that uses the app.
Cost

What it really costs

The trigger never costs a task, however many events arrive. Zapier bills the actions that succeed, one task each.

  • Premium appNo, it works from the free plan (Zapier marks it beta)
  • Free plan100 tasks a month, two-step Zaps
  • Instant triggers11 of 11

An action that fails is not counted. A Zap with three actions uses three times what a one-action Zap uses. The free plan gives 100 tasks a month and Zaps of two steps, one trigger and one action; a second action or a filter makes the Zap multi-step, and that needs a paid plan. The interval grid only concerns polling triggers, and none of the 11 here poll. Access PaySuite - Direct Debit is not a premium app, so it runs from the free plan.

Connect

Connect your Access PaySuite account

  1. 01

    Open Apps and add a connection

    In Zapier, go to the Apps page of your account and click + Add connection. Type Access PaySuite - Direct Debit in the search box of the dialog and pick it from the results.

  2. 02

    Sign in on the Access PaySuite side

    Click Add connection. A new tab opens: sign in with the account that holds your contracts. You need an account on the app, plus read or write access on any record you do not own yourself and want the Zap to touch.

  3. 03

    Grant access, then reuse it

    Allow Zapier to reach the account. The connection is now saved once, and every later step that uses Access PaySuite, in this Zap or the next one, offers it in its account list.

First Zap

Your first Zap: from new customer to first collection

GoalEvery new customer gets a contract and a first payment, without anyone opening Access PaySuite.

  1. 01

    Start the Zap on Customer Created

    Build a new Zap, choose Access PaySuite - Direct Debit as the app that starts it and Customer Created as the event, then pick the connection set up above.

  2. 02

    Test the trigger on a real customer

    Run the test. Zapier brings back the three most recent items of the connected account; pick a real customer so the next steps are mapped on actual data.

  3. 03

    Add Create Contract

    Add the action Create Contract. Map the customer's GUID from the trigger step if the test shows one, set a Start Date at least 10 UK working days out, and answer the other required fields.

  4. 04

    Chain Create New Payment

    Add a second action, Create New Payment, with the Contract ID (GUID) mapped from the previous step if its test returns one, an Amount and a Date of Collection. Two actions make this a multi-step Zap, so it needs a paid plan.

  5. 05

    Test each step, then publish

    Test each action once and read what came back before going further. Then publish the Zap to switch it on: from that moment, each new customer runs it.

Triggers

The 11 triggers, one by one

11 events start a Zap when something happens in Access PaySuite - Direct Debit, and 11 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Contract Created

Instant trigger

In Zapier“Triggers when there's a new contact created.”

Starts a Zap as soon as a new direct debit contract exists in Access PaySuite, whether someone set it up by hand or another Zap created it. One new contract, one run.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
the sales team or a welcome sequence should know the minute a customer commits to a regular collection.
Watch out
contracts your own Zaps open with Create Contract fire it too, so make sure the same signup is not counted twice.
2

Customer Created

Instant trigger

In Zapier“Triggers when there's a new customer created.”

A new payer added to the account is the signal here: each customer record created in Access PaySuite opens one run of your Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a gym copying every new member into its booking tool and mailing list, without anyone retyping a name.
Watch out
a customer can exist before any contract does, so a Zap built on this event should not count on a collection amount being there yet.
3

Customer Amended

Instant trigger

In Zapier“Triggers when there's a new customer amended.”

Hands your Zap every edit made to a customer already on file. Brand new customers belong to the previous trigger, not to this one.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keep the address or email in your CRM in line with what the payer told your accounts team on the phone.
Watch out
answering with Update Customer on that same record edits it again, and the trigger fires once more: a loop that eats tasks.
4

Contract Amended

Instant trigger

In Zapier“Triggers when there's a contact amended.”

When a contract that already exists is changed in Access PaySuite, this trigger passes the change on. One amendment, one run.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
warn the account manager that a payer's terms have moved, so the next receipt or invoice matches the contract.
Watch out
the Update Contract actions of this app amend contracts too, so pairing them with this trigger on the same contract can set the Zap off again and again.
5

Contract Cancelled

Instant trigger

In Zapier“Triggers when there's a canceled contract.”

Reacts to the end of an agreement: once a direct debit contract is cancelled, your Zap runs.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
close the membership in your booking tool, or open a follow-up task for whoever calls lapsed customers.
Watch out
a contract cancelled before the Zap went live never shows up; a Zap only sees what happens after it is published, so older cancellations need a separate clean-up.
6

Payment Cancelled

Instant trigger

In Zapier“Triggers when there's a payment cancelled.”

Here the event is narrower: a single payment called off, while the contract around it may carry on.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
tell the bookkeeper, so the income expected for the month is corrected before anyone builds a forecast on it.
Watch out
a cancelled contract and a cancelled payment are two separate triggers; build on the one that matches the event your team actually acts on.
7

Payment Created

Instant trigger

In Zapier“Triggers when there's a new payment created.”

Each new payment scheduled in the account starts one run, including payments that a Zap of yours added with Create New Payment.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
log every upcoming collection in a shared spreadsheet so the cash forecast stays current without a weekly export.
Watch out
if the Zap answering this trigger itself creates payments, each new payment starts it again; keep the two jobs in Zaps that never touch each other.
8

Payment Failed

Instant trigger

In Zapier“Triggers when there's a payment failed.”

The trigger with the most money at stake: a collection that does not go through goes straight to your Zap, so nobody has to spot it in a report.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
alert credit control or send the payer a reminder while the problem is still fresh.
Watch out
re-presenting the payment with Create New Payment is an ordinary action: it uses one task and needs a new Date of Collection that you choose.
9

Payment Submitted to Bank

Instant trigger

In Zapier“Triggers when there's a payment submitted to bank.”

Runs once Access PaySuite has passed a payment to the bank, the stage that follows scheduling.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
update a status column so customer support can tell a caller the collection has been sent to the bank.
Watch out
submitted is not the same as failed or settled; a Zap that marks an invoice as paid at this stage marks it too early.
10

Payment Updated

Instant trigger

In Zapier“Triggers when there's a payment updated.”

Any change to an existing payment, as opposed to a brand new one, sends a run into your Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
mirror an edited payment into the sheet your accountant works from, so both sides hold the same figures.
Watch out
new payments start Payment Created instead, so a complete log needs this trigger and that one, each in its own Zap.
11

Rolling Payment Created

Instant trigger

In Zapier“Triggers when there's a rolling payment created.”

Reserved for rolling payments, as Access PaySuite labels them: each new one starts your Zap, apart from the ordinary payments of Payment Created.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keep rolling payments in their own tab of your reporting when some of your contracts produce them.
Watch out
the app's Zapier listing gives no definition of a rolling payment; check in your account which contracts create them before you build on this event.
Actions

The 10 actions, grouped by what they do

Access PaySuite - Direct Debit gives you 10 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Cancel Contract

Action

In Zapier“Cancels the Contract (Does not cancel payment creation)”

Ends a contract identified by its Contract ID, the only field it asks for.

When to use it
a membership is closed in your booking system and the direct debit should stop with it.
Watch out
by the app's own description, cancelling the contract does not cancel payment creation, so check what is already scheduled.
2

Update Contract Amount

Action

In Zapier“Amends an existing Contract amount.”

Changes how much an existing contract collects. Contract ID, the new Amount and a Comment are all required.

When to use it
a customer moves to a dearer or cheaper plan in your sales tool.
Watch out
since the Comment is mandatory, decide what text the Zap writes there, or every change carries the same vague note.
3

Update Contract Date (Annual Schedules)

Action

In Zapier“Amends an existing Contract payment date (Annual Schedules)”

Moves the payment date of a contract on an annual schedule, through a Month Day and a Month, with a required Comment.

When to use it
a yearly subscription renews on a new date agreed with the customer.
Watch out
three date actions exist, one per schedule; this one is for annual contracts only.
4

Update Contract Date (Monthly Schedules)

Action

In Zapier“Amends an existing Contract payment date (Monthly Schedules)”

The monthly sibling: it shifts the day of the month a contract collects on, with a Comment that is required.

When to use it
a payer asks to be charged after payday rather than at the start of the month.
Watch out
only Month Day is asked, so pick this version for monthly contracts and no other.
5

Update Contract Day (Weekly Schedules)

Action

In Zapier“Update Contract Day (Weekly Schedules)”

For weekly contracts, this action changes the Day the collection falls on, and wants a Comment as well.

When to use it
a weekly class moves from Monday to Thursday and the payments should follow.
Watch out
Patch Next Payment is optional and the app's Zapier listing does not explain it; test on one contract first.
6

Update Contract Reference

Action

In Zapier“Update Direct Debit Reference”

Replaces the direct debit reference of a contract with a New DDRef, the identifier that follows the customer and contract for their whole life.

When to use it
if you use Xero or FreshBooks, align it with the Account Reference there.
Watch out
the reference has to be unique for the client, so a duplicate will not do.
7

Create Contract

Action

In Zapier“Creates a Contract for a Customer (ad-hoc or scheduled).”

Opens a contract, ad hoc or scheduled, for a customer who already exists. Five fields are mandatory, and the Customer ID (GUID) is meant to come from the step that created the customer.

When to use it
right after a signup, so the agreement exists before anyone forgets it.
Watch out
the Start Date must sit at least 10 UK working days ahead.
8

Get Customer Sign Up Link

Action

In Zapier“Returns a Sign Up Link with prepopulated fields and optionally sends an email the the customer.”

Returns a sign-up link with fields already filled in, and can email it to the customer when Send Email is switched on.

When to use it
a lead says yes in your CRM and should receive the direct debit form without a phone call.
Watch out
leave Send Email off if another step of the Zap is the one meant to write to the customer, or they get two messages.
9

Create New Payment

Action

In Zapier“Creates a new payment in DDCMS”

Adds a payment to a contract: you hand it the Contract ID (GUID), an Amount and a Date of Collection.

When to use it
charge a one-off fee on top of the schedule, or try again after a failed collection.
Watch out
with no search step on this app, that GUID has to be mapped from an earlier step or typed by hand.
10

Update Customer

Action

In Zapier“Updates a customer in DDCMS.”

Edits a customer already on the account, found through its Customer ID, the GUID of the record to change.

When to use it
a payer corrects their details in your CRM and Access PaySuite should follow.
Watch out
a Zap that starts on Customer Amended and ends here can loop on the same record.
When it breaks

When the Zap breaks

Three ways a direct debit Zap goes wrong, and none of them shows up in the editor.

Zapier attaches no help article to this app and lists no limit of its own, so the cases below are the general ones that apply to every Zap. Each one bites hard on payment data. For error screens and stuck runs, the Zapier troubleshooting page goes further.

  • No catching up on the past

    A Zap only reacts to what happens after it is switched on. Contracts and payments that already existed are never picked up; moving them is a separate job.

  • The Zap that feeds itself

    Contract Amended followed by Update Contract Amount on the same contract amends it again, which fires the trigger again and burns through the task count fast.

  • A sudden flood held back

    After a bulk import or a migration, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection. Plan big loads apart from the Zap.
Need help

Need help automating Access PaySuite - Direct Debit with Zapier?

A person reads every message.

FAQ

Questions people ask before connecting

01Is the Access PaySuite - Direct Debit Zapier integration free?
Yes, for a simple Zap. Access PaySuite - Direct Debit is not a premium app, so it works from the free plan, which gives 100 tasks a month and Zaps of two steps: one trigger, one action. As soon as you add a second action or a filter, the Zap becomes multi-step and needs a paid plan. Zapier marks the app as beta, so expect it to change. Prices are left out on purpose: the grids move too often to be worth printing.
02How many tasks does an Access PaySuite Zap use?
One per action that succeeds, and nothing for the trigger. Payment Failed firing a hundred times costs nothing on its own; it is the actions behind it that count. A Zap that creates a contract and then a payment uses two tasks per run, one that also updates a customer uses three. An action that fails is not billed. A few apps and actions take more than one task, so the task history of your account is the place to check the real figure.
03Do Access PaySuite triggers run in real time?
Yes. All 11 triggers are instant: Access PaySuite calls Zapier the moment the event happens, and the editor shows a lightning bolt on them. The polling interval, 15 minutes on the free plan, does not apply to any of them. That is the most useful thing to know on a free plan here: a failed payment reaches your Zap as quickly as it would on Enterprise. The type is set by the app itself and cannot be changed from the editor.
04What does connecting an Access PaySuite account require?
An account on Access PaySuite, plus read or write access on any record you do not own and want the Zap to touch. In Zapier, open the Apps page, click + Add connection, search for Access PaySuite - Direct Debit and pick it, then click Add connection. Sign in to the app in the tab that opens and grant Zapier access. The connection is saved once and reused by every step that uses the app, in this Zap and the next ones.
05How far ahead must the Start Date of a new contract be?
At least 10 UK working days ahead of the day the Zap runs. Create Contract treats Start Date as a required field and expects the format YYYY-MM-DDT00:00:00.000. A Zap that maps the trigger date straight into it hands the action a date it does not accept, so add the gap before mapping. The same action also requires Customer ID (GUID), Is Gift Aid, Termination Type and At The End, which makes it the most demanding action of the app.
06What if the operation you need is not in the list?
Then Zapier cannot do it with this app today. The list holds 11 triggers and 10 actions, and no search step: a Zap cannot find an existing contract or customer by name, so every ID has to come from an earlier step or be typed. There is no delete action either. The usual way around is to let another app of the Zap hold the IDs, or to handle the missing operation in Access PaySuite by hand while the Zap covers the rest.
07Zapier, Make or n8n for Access PaySuite?
It depends on criteria, not on a winner. On Zapier, this app is ready with 11 instant triggers and 10 actions, works from the free plan for two-step Zaps, and bills per successful action. Whether Make or n8n offer a ready connector for Access PaySuite is not covered by this page, so check their app lists first. Then compare how each tool bills, who hosts it, and who on your team will maintain the workflow once it runs.
Same platform

Other docs you might need on this stack.

Browse all integrations