--- title: "PayFunnels Integration" description: "PayFunnels is a payment-link and subscription platform. Agents create one-time, recurring, plan, and pay-what-you-want links, list and refund payments, cancel, pause, and resume subscriptions, and read setup and processing fees." url: https://flowrunner.ai/integrations/payfunnels date_modified: 2026-09-04T14:51:36-07:00 --- # PayFunnels [Payments](https://flowrunner.ai/integrations/category/finance-accounting) PayFunnels is a payment-link and subscription platform. Agents create one-time, recurring, plan, and pay-what-you-want links, list and refund payments, cancel, pause, and resume subscriptions, and read setup and processing fees. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 26 actions · API key · available [PayFunnels website](https://payfunnels.com/) · [Platform Documentation](https://api.payfunnels.com/docs) · Capability data verified 2026-08-25 1. A product price or lineup changes in the source catalog 2. Agent reads the affected payment links and their current product sets with Get Payment Link 3. Agent diffs the catalog against each link and lists additions, patches, and removals 4. Agent confirms which links are live and how many successful payments each has taken 5. Links whose diff removes nothing are updated unattended 6. Every proposed removal posts to the revenue channel with the link's payment count 7. The revenue owner approves the removals, because omitted products are deleted ## What This Integration Enables PayFunnels is opinionated about one thing: a payment link is not a single shape. There are six creation routes, and each encodes a different commitment. A one-time link takes one fixed payment. A recurring link bills forever. A payment plan link bills a fixed number of times and then cancels itself. A custom plan link charges an amount immediately and then follows a schedule you define. A pay what you want link lets the customer set the figure. A multiple products link offers several at once, with a selection rule the vendor quietly disables when you mix recurring and plan products. That taxonomy is the reason to automate here rather than click through a dashboard. FlowRunner agents pick the shape the situation calls for, keep the product sets on live links in step with the catalog, work the failed payment list as a dunning queue, and manage the subscription lifecycle through cancel, pause, and resume. The pause behavior alone is a revenue decision rather than a switch, which is where [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) belongs on a subscriptions connector. ### Without FlowRunner **Link inventory unmapped**: Nobody can say which live links carry a product until someone opens each one **Price edits done by hand**: A price change means visiting every link that offers the product and hoping none was missed **Failed payments noticed late**: Declines sit in a list that gets reviewed when someone remembers to look ### With FlowRunner **Inventory read before writing**: Each link is read, diffed, and reported before a single field is changed **Edits proposed and approved**: The agent assembles the exact product set and a person signs off on what disappears **Declines worked as a queue**: The failed list is polled on a schedule and each one becomes a tracked follow-up ## Use Case Scenarios ### The right link shape for the offer A new offer is approved. The agent reads its terms and chooses the route rather than defaulting to one. A pilot that should end by itself becomes Create Payment Plan Link, which bills a fixed number of times and cancels itself, so nobody has to remember to stop it. An open-ended retainer becomes Create Recurring Payment Link. A community donation becomes Create Pay What You Want Link with recurring switched on so a supporter can choose to give monthly. If the offer carries an onboarding charge, Create Setup Fee runs first and its identifier is attached to the link. The finished URL posts into [Slack](https://flowrunner.ai/integrations/slack) and onto the deal record in [HubSpot](https://flowrunner.ai/integrations/hubspot). ### Dunning that actually gets worked On a schedule, the agent calls List Payments filtered to failed, which is the dunning queue in practice. For each one it reads Get Payment for the full breakdown, then reads the customer's subscription with Get Subscription and compares the total due against the total subscription amount, which is the arrears picture on a payment plan. Accounts inside a grace window get a reminder over [Brevo](https://flowrunner.ai/integrations/brevo). Accounts past it are assembled into a review list with the amount owed, the cycles remaining, and the payment history, and posted for a person to decide between another attempt, a pause, and a cancellation. ### A refund that does not fall through the unit trap A refund is agreed in support. The agent reads the payment with Get Payment, which breaks out the tax, the setup fee, the processing fee, and anything already refunded, so the figure it proposes is the actual remaining balance rather than the headline price. It then converts to the smallest currency unit, because Refund Payment takes cents while every payment link amount is in the major unit, and a naive pass would return twenty five cents where twenty five dollars was meant. It supplies one of the three reasons the card networks recognize, and posts the confirmed refund back into the [Zendesk](https://flowrunner.ai/integrations/zendesk) ticket. ## Human-in-Loop Highlight Update Payment Link has one field that behaves in three ways, and the dangerous behavior is the default. Send a product with only its identifier and it is kept. Send it with fields and it is patched. Send one with no identifier and it is added. Leave one out entirely and it is deleted. So an agent syncing prices from a catalog, sending the products it knows about, silently strips every product it does not know about from a live link that customers are paying through. Nothing in this action list restores them, and Get Payment Link is the only record of what was there. So the agent never writes the set it built. It writes the diff to a person first: "Link 'Spring Cohort' currently offers four products and has taken 38 successful payments. The catalog sync would keep three, patch one price, and remove 'Alumni Pass', which is not in the source. Approve the removal?" The revenue owner answers, and a product disappears from a live link only because someone chose to remove it. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 26 actions ### Payment Links 10 - **Create One-Time Payment Link** Creates a link that takes a single fixed payment. - **Create Recurring Payment Link** Creates a subscription link that bills on an interval indefinitely. Trial days must be more than two, since the vendor rejects one or two. - **Create Payment Plan Link** Creates an installment link that bills a fixed number of times and then cancels itself. The difference from a recurring link is that this one ends on its own. - **Create Custom Plan Payment Link** Creates a link with your own payment schedule: an amount charged immediately, then whatever timetable you define. Note that the vendor charges the opening amount straight away, unlike the other recurring types. - **Create Pay What You Want Link** Creates a link where the customer sets the amount. One-time giving is allowed by default and recurring is not, so switch the second on to let a supporter choose to give monthly. - **Create Multiple Products Link** Creates a link offering several products at once. The multiple selection setting is conditional: the vendor treats it as off when you mix recurring and payment-plan products, and when it is on, all recurring intervals must match. - **List Payment Links** Lists your payment links, optionally of one kind. Twenty five come back by default, so set the limit for more. - **Get Payment Link** Retrieves one payment link, including how many successful payments it has taken. - **Update Payment Link** Updates a payment link. Its products list carries three behaviors in one field: an identifier alone keeps a product, an identifier with fields patches it, a product with no identifier adds one, and anything left out is deleted. - **Delete Payment Link** Deletes a payment link so it can no longer be paid. ### Payments and Refunds 3 - **List Payments** Lists payments, optionally only the succeeded or only the failed ones. Twenty five come back by default, and the failed list is the dunning queue. - **Get Payment** Retrieves one payment in full, with its tax, setup fee, processing fee, and refunded amounts broken out separately. - **Refund Payment** Refunds a payment in full or in part. The amount here is in the smallest currency unit while payment link amounts are in the major unit, and the reason is required and must be one of the three the card networks recognize. ### Subscriptions 5 - **List Subscriptions** Lists subscriptions with their collected, due, and maximum amounts. The total due against the total subscription amount is the arrears picture for a payment plan. - **Get Subscription** Retrieves one subscription. - **Cancel Subscription** Cancels a subscription now, at the end of the billing period, or on a date you choose. A cancellation date is required, and used, only when the custom date option is selected. - **Pause Subscription** Pauses a subscription. The behavior is a billing decision rather than a display one: voiding stops service and bills nothing, keeping it as a draft keeps service free, and marking it uncollectible holds the debt so it can be collected later. Leave the resume date empty to resume by hand. - **Resume Subscription** Resumes a paused subscription. Whether the customer is billed for the pause depends on the behavior it was paused with and on the unpaid invoice setting, not on this call. ### Fees 8 - **Create Setup Fee** Creates a one-time setup fee that recurring and payment-plan links can attach. Its identifier is what those links take as their setup fee product. - **List Setup Fees** Lists your one-time setup fees, twenty five per page by default. - **Get Setup Fee** Retrieves one setup fee. - **Update Setup Fee** Renames a setup fee or makes it the default. The amount and currency cannot be changed, since the vendor publishes only the name and the default flag here, so a price change means a new fee. - **Delete Setup Fee** Deletes a setup fee. - **List Processing Fees** Lists the processing-fee rules on the account. Read the use-amount flag first, since it decides whether the fixed amount or the percentage applies. These are read only through the API. - **Get Default Processing Fee** Returns the account's default processing fee, the one a payment link applies when forwarding processing fees is on. - **Get Processing Fee** Retrieves one processing-fee rule. ## Frequently Asked Questions ### What can FlowRunner do with PayFunnels? FlowRunner agents can run Create One-Time Payment Link, Create Recurring Payment Link, and Create Payment Plan Link in PayFunnels, plus 23 more actions. ### Does connecting PayFunnels to FlowRunner require OAuth? No. PayFunnels connects to FlowRunner with an API key, no OAuth flow required. ### Can PayFunnels trigger a FlowRunner workflow automatically? PayFunnels doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at PayFunnels?** This integration exposes PayFunnels to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/payfunnels. Site index: https://flowrunner.ai/llms.txt