GoCardless
PaymentsConnect AI agents to GoCardless bank-to-bank payments. Agents set up Direct Debit mandates, take one-off, recurring, and instalment payments, issue refunds, reconcile payouts, and run hosted or own-page authorisation flows, with six event triggers that react to payment, mandate, subscription, refund, payout, and billing-request activity.
What This Integration Enables
Agents run the Direct Debit lifecycle end to end. They create customers and save bank details, set up and cancel mandates, and migrate mandates from another provider in bulk. They charge one-off payments against a mandate, run subscriptions and instalment schedules, cancel and retry payments, and issue refunds. They reconcile payouts down to the individual line items, run hosted or own-page authorisation flows to collect bank details, and react to payment, mandate, subscription, refund, payout, and billing-request events. The agent handles the routine collection and reconciliation, and stops before money moves back to a payer.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Failed-payment recovery
A payment fails and When a Payment Event Happens fires. The agent reads the failure reason and decides whether it is retryable. For a retryable failure it calls Retry Payment; for others it sends the customer a failed-payment notice through [Gmail](https://developer.gocardless.com/api-reference) and logs the outcome to [Google Sheets](/integrations/google-sheets) "Add Row". Failures that used to be handled the same way now get routed by reason, and the ones that need a human are the only ones a person sees.
Onboarding new subscribers
A batch of new subscribers is ready to set up on recurring Direct Debit. The agent reads the list with [Google Sheets](/integrations/google-sheets) "Get Rows", then calls Create Customer and Create Subscription to set each one up. Onboarding that used to be a manual entry per subscriber becomes a single pass the agent runs.
Payout reconciliation
A payout lands in your bank account and When a Payout Event Happens fires. The agent reconciles the transfer by posting a matching payment in [QuickBooks Online](/integrations/quickbooks-online) with "Create Payment", then alerts the finance channel with [Slack](/integrations/slack) "Send Message To Channel". It can drill into List Payout Items to match every payment, refund, and fee that adds up to the total. The reconciliation that meant matching a bank line against a spreadsheet becomes part of the flow.
Human-in-Loop Highlight
In GoCardless the routine motions are safe to automate: charging a mandate, retrying a failure, running a subscription. The one that carries real cost is the refund, because it moves money back out and cannot be undone casually. Configure the agent to pause before Create Refund. It sends the finance reviewer the original payment, the amount, and the customer's history through Slack and asks: "This refund is ready to issue against the payment shown. Approve it?" A person approves or modifies the amount, and the agent issues exactly the refund that was confirmed. The approver and the reason are written to the audit trail. This is [human-in-the-loop](/concepts/human-in-the-loop): the agent pauses on its own, gathers the context and the choices, routes to the right person, and resumes the moment they answer.
Agent Capabilities
61 actionsCustomers
9- List Customers Lists your GoCardless customers. Used to export or reconcile customer records.
- Get Customer Retrieves one customer's full profile, including name, email, and address. Used to read a payer inside a workflow.
- Create Customer Creates a new customer, the first step before collecting bank details. Used to onboard a payer.
- Update Customer Updates a customer's profile fields such as name, email, or address. Used to keep payer details current.
- Remove Customer Removes a customer. Used to clean up a record created in error.
- List Customer Bank Accounts Lists bank accounts attached to your customers. Used to review a payer's saved accounts.
- Get Customer Bank Account Retrieves one customer bank account, including sort code and status. Used to confirm account details.
- Save Customer Bank Account Saves a customer's bank details so you can charge them. Used to register a payer's account.
- Disable Customer Bank Account Permanently turns off a customer bank account. Used to retire an account that should no longer be charged.
Mandates
7- List Mandates Lists Direct Debit mandates. Used to review active payer authorisations.
- Get Mandate Retrieves one mandate, including scheme, status, and next earliest charge date. Used to check a mandate before charging.
- Create Mandate Creates a Direct Debit mandate against an existing customer bank account. Used to authorise collection from a payer.
- Update Mandate Notes Updates the notes attached to a mandate. Used to annotate a mandate for the team.
- Cancel Mandate Cancels a mandate so no further payments can be taken. Used to end collection from a payer.
- Reinstate Mandate (UK Bacs) Brings back a cancelled or failed UK Bacs mandate without a new sign-up. Used to recover a lapsed mandate.
- Get Mandate PDF Generates a downloadable PDF of a signed mandate. Used to store proof of authorisation.
Mandate Imports
6- Create Mandate Import Starts migrating existing mandates from another provider into GoCardless. Used to begin a bulk mandate migration.
- Get Mandate Import Retrieves the status of a mandate import. Used to track a migration's progress.
- Submit Mandate Import Finishes adding entries and hands the import to GoCardless. Used to submit a completed migration.
- Cancel Mandate Import Aborts a mandate import before it is submitted. Used to cancel a migration in progress.
- Add Mandate Import Entry Adds one existing mandate to an open import. Used to build up a migration entry by entry.
- List Mandate Import Entries Lists every entry in a mandate import and its result. Used to verify a migration's outcome.
Creditors
3- List Creditors Lists your creditor accounts and their verification status. Used to review payout destinations.
- Get Creditor Retrieves one creditor account, including verification status. Used to confirm a creditor can receive payouts.
- Update Creditor Updates a creditor's trading name, address, or payout account. Used to keep payout settings current.
Payments
6- List Payments Lists payments you have collected. Used to review or export collection activity.
- Get Payment Retrieves one payment, including amount, status, and charge date. Used to read a payment in a workflow.
- Create Payment Charges a one-off payment against an active mandate. Used to collect an ad-hoc amount.
- Update Payment Updates a payment's notes or auto-retry behaviour. Used to adjust a pending payment.
- Cancel Payment Cancels a payment before the money reaches you. Used to stop a collection in error.
- Retry Payment Retries a failed payment. Used in a recovery flow for retryable failures.
Subscriptions
7- List Subscriptions Lists recurring subscriptions. Used to review active recurring billing.
- Get Subscription Retrieves one subscription, including amount, interval, and upcoming charge dates. Used to check subscription state.
- Create Subscription Sets up a recurring subscription. Used to start recurring Direct Debit billing.
- Update Subscription Updates a subscription's name, reference, amount, or notes. Used to adjust an active subscription.
- Pause Subscription Pauses a subscription temporarily. Used to hold billing during a dispute or retention path.
- Resume Subscription Resumes a paused subscription. Used to restart billing after a hold.
- Cancel Subscription Cancels a subscription so no more charges are generated. Used to end recurring billing.
Instalment Schedules
4- List Instalment Schedules Lists instalment schedules. Used to review payment plans.
- Get Instalment Schedule Retrieves one instalment schedule and its generated payments. Used to check a plan's status.
- Create Instalment Schedule Sets up a fixed payment plan against one mandate. Used to spread a charge over instalments.
- Cancel Instalment Schedule Cancels an instalment schedule so no further instalments are collected. Used to stop a payment plan.
Refunds
3- List Refunds Lists refunds you have issued. Used to review refund activity.
- Get Refund Retrieves one refund. Used to read a refund's details.
- Create Refund Refunds a confirmed or paid-out payment. Used behind a human gate to return funds to a payer.
Payouts
3- List Payouts Lists payouts from GoCardless to your bank account. Used to review settlements.
- Get Payout Retrieves one payout, including amount, fees, and arrival date. Used to read a settlement.
- List Payout Items Lists the line items inside a payout: every payment, refund, and fee. Used to reconcile a payout to the penny.
Billing Requests
8- Create Billing Request Sets up a hosted onboarding session. Used to start collecting a payer's details.
- Get Billing Request Retrieves one billing request to check its status. Used to track an onboarding flow.
- Create Hosted Flow URL Generates a hosted GoCardless URL for a billing request. Used to send a payer a self-serve onboarding link.
- Cancel Billing Request Cancels a billing request. Used to abandon an onboarding flow.
- Finalise Billing Request Manually finalises a billing request, creating the mandate or taking the payment. Used to complete onboarding from your own flow.
- Collect Customer Details (Own Pages) Completes the customer-details step from your own pages. Used to run onboarding without the hosted flow.
- Collect Bank Account (Own Pages) Completes the bank-account step from your own pages. Used to submit payer bank details you collected.
- Confirm Payer Details Records that the payer confirmed the details, a Direct Debit compliance step. Used to complete an own-pages onboarding.
Events
2- List Events Lists events: the timeline of state changes across mandates, payments, subscriptions, payouts, and refunds. Used to audit activity.
- Get Event Retrieves one event by ID. Used to read a specific state change.
Utility
3- Test Connection Checks that the connection is working. Used to verify credentials before a run.
- Lookup Bank Looks up bank information from an IBAN or local account number. Used to validate a payer's bank before collecting.
- Run Test Scenario (Sandbox Only) Forces a resource into a specific state in the sandbox. Used to test workflows against known states.
Triggers
6 triggersEvent Triggers
6- When a Payment Event Happens Fires when a payment changes state in GoCardless, such as being submitted, confirmed, paid out, failed, charged back, or cancelled. Starts a workflow to notify the customer, retry a failed collection, or reconcile a confirmed payment.
- When a Mandate Event Happens Fires when a Direct Debit mandate changes state, such as being created, activated, cancelled, expired, or failed. Starts a workflow to onboard a payer once a mandate is active or follow up when one fails.
- When a Subscription Event Happens Fires when a subscription changes state, such as being created, paused, resumed, cancelled, or finishing. Starts a workflow to update the customer record or adjust downstream billing.
- When a Refund Event Happens Fires when a refund changes state, such as being created, submitted, paid, or failed. Starts a workflow to notify the customer and record the refund against the original payment.
- When a Payout Event Happens Fires when a payout to your bank account is paid. Starts a reconciliation workflow that matches the settled amount against expected payments.
- When a Billing Request Event Happens Fires when a billing request changes state during a hosted or own-page flow, such as being fulfilled or cancelled. Starts a workflow to complete customer onboarding once bank details are collected.
Start building with GoCardless
$100 in credits. No card required. Connect in minutes.