Resources · Zapier integration

Partial.ly Zapier integrationAutomate Partial.ly with Zapier.

The Partial.ly Zapier integration gives you 8 triggers, 2 actions and 1 search. All 8 triggers are instant: a failed payment, a defaulted plan or an abandoned checkout reaches your other tools straight away, even on the free Zapier plan.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Partial.ly Zapier integration does for you

Partial.ly sells on instalments: your customers pay in several parts instead of all at once. Zapier sits next to it and listens. When something happens to a plan or a payment, it passes the news to another app, or it creates and updates plans for you, without a line of code.

Collections that start on time. Payment Failed and Payment Plan Defaulted reach the person who chases late payers at the moment Partial.ly records them, not at the end of the month when someone opens a report.

A second shot at lost checkouts. Checkout Abandoned fires when a customer leaves a plan checkout unfinished within the delay set in your account. Chain it to Create a Payment Plan and the customer can get a new plan request by email.

A clean file when a plan closes. Payment Plan Paid and Payment Plan Canceled tell your bookkeeping sheet or your CRM that the story is over, whichever way it ended.

What Zapier does not do for Partial.ly: it cannot delete a plan or refund a payment. The editor offers 2 actions and 1 search, and that search only finds a plan by its ID, never by customer name or email. A Zap also ignores everything that happened before you switched it on.

Comparing tools before you commit? The Make vs Zapier and n8n vs Zapier pages are there.

Vocabulary

Zapier vocabulary in one minute

Eight words you will meet in the editor, in plain English.

Zap
The automation you build: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, here a payment or a plan change.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you, like creating a plan.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts those.
Instant trigger
A trigger the app reports itself: it calls Zapier the moment the event happens, so nothing waits for a check.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. Partial.ly has none.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Cost

What a Partial.ly Zap really costs

The trigger never costs a task. You pay for each action that succeeds, and an action that fails is not counted.

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Paid-only appNo

The free plan gives 100 tasks a month, but every Zap stays at two steps: one trigger, one action. A filter, a second action or Find a Payment Plan turns it into a multi-step Zap, which needs a paid plan. Since every Partial.ly trigger is instant, the polling grid below never slows you down. A Zap that writes back into what its own trigger watches can also eat your quota fast. On paid plans you can change how often polling checks run, but Partial.ly never needs it.

Connect

Connect your Partial.ly account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Partial.ly account linked once, then reused by every Zap that touches it.

  2. 02

    Pick Partial.ly

    Type Partial.ly in the search box of the dialog, select it, then click Add connection. You need a Partial.ly account first, plus access to any plan you did not create yourself.

  3. 03

    Sign in and allow access

    Sign in to Partial.ly in the tab that opens and grant Zapier access to the account. The connection now shows up in the list, ready for the first Zap. It stays there for every Zap after that one.

First Zap

Your first Zap: recover an abandoned checkout

GoalWhen a customer leaves a payment-plan checkout unfinished, create a new plan for them and email them the request.

  1. 01

    Build: choose the trigger

    Pick Partial.ly as the app and Checkout Abandoned as the event that starts the Zap, then select the connection you just added.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of your account, so you map the next steps on a real abandoned checkout rather than an empty one.

  3. 03

    Add a filter

    From the plus icon, add Filter. Fill the three boxes: the field to look at, the rule, the value. Use a text rule on text and a number rule on numbers. This step needs a paid plan.

  4. 04

    Add the action

    Choose Create a Payment Plan. Fill Offer ID, Plan amount and Customer email from the earlier steps, and switch on Send customer plan request so the customer gets the email.

  5. 05

    Test, then publish

    Test the action and read what came back in Partial.ly. If the plan looks right, click Publish to switch the Zap on. Until then, nothing runs.

Triggers

Partial.ly triggers

8 events start a Zap when something happens in Partial.ly, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Checkout Abandoned

Instant trigger

In Zapier“Triggers when a customer does not complete a payment plan checkout within the configured amount of time.”

A customer opened a payment-plan checkout and left before finishing it within the time limit set in your Partial.ly account. The Zap receives that lost sale while it is still fresh.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
hand the lead to a sales rep who calls back, or rebuild the plan with Create a Payment Plan and let the customer try again.
Watch out
the delay that counts as abandoned is configured in Partial.ly, not in Zapier, so adjust it there if the Zap runs too early or too late.
2

Installment Upcoming

Instant trigger

In Zapier“Triggers when an installment is upcoming.”

Here the news comes before the money moves: Partial.ly signals an instalment that is about to fall due. It is your chance to warn the customer before the charge, not after a failure.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
send a friendly reminder by text or email, or add the due payment to a cash-flow sheet.
Watch out
the Zapier page does not say how far ahead an instalment counts as upcoming, so test it on a real plan before you promise customers a reminder date.
3

Payment Failed

Instant trigger

In Zapier“Triggers when a payment fails.”

Every time a charge on a plan does not go through, this trigger starts the Zap. It is the earliest sign that a customer may slide into default.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
ping whoever handles collections in your team chat, or open a follow-up task in your CRM so nobody forgets the customer.
Watch out
the same plan can fail more than once, and each failure runs the Zap again, so every action it carries costs a task each time.
4

Payment Succeeded

Instant trigger

In Zapier“Triggers when a payment is successfully processed.”

The good-news trigger: a payment on one of your Partial.ly plans went through, and the Zap picks it up at once.

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 each payment in your accounting sheet, or post a line in the channel your finance team watches.
Watch out
this is likely your busiest trigger, since every payment on every plan runs the Zap; on the free plan, 100 tasks a month can go quickly.
5

Payment Plan Canceled

Instant trigger

In Zapier“Triggers when a payment plan is canceled.”

When someone cancels a payment plan, this event closes the loop for the tools that still think the plan is alive.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
stop reminder sequences in your email tool and switch the customer status in your CRM, so nobody chases a plan that no longer exists.
Watch out
a cancellation is not a default; a plan that stops because of repeated failed payments comes through Payment Plan Defaulted instead, so cover both if you want every ended plan.
6

Payment Plan Defaulted

Instant trigger

In Zapier“Triggers when a payment plan is defaults due to multiple failed payments.”

Several payments in a row have failed and Partial.ly marks the plan as defaulted. For your cash flow, this is the event that matters most.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
move the file to your collections process, alert the account owner, or add the customer to a list that blocks new orders.
Watch out
a defaulted plan can be reopened later, and that reopening comes back through Payment Plan Opened, not through this trigger.
7

Payment Plan Opened

Instant trigger

In Zapier“Triggers when a payment plan is opened. Note that this will be sent when a new plan is opened for the first time, as well as when an existing plan is re-opened (a defaulted plan being reopened, for example).”

This one runs when a customer opens a payment plan, which is the start of the commitment. It also runs when an existing plan is reopened, for example after a default.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
send a welcome email with the payment schedule, or create the customer record in your CRM.
Watch out
because reopened plans fire it too, a welcome Zap can greet a returning customer a second time; word the message so it still makes sense then.
8

Payment Plan Paid

Instant trigger

In Zapier“Triggers when a payment plan is fully paid.”

The last instalment has landed and the plan is fully paid. The trigger fires once, at the very end of the plan, not on each 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
send a thank-you note, release a product that ships only once paid, or mark the deal as closed.
Watch out
if you want a record of every single instalment, Payment Succeeded is the trigger for that; this one only tells you the plan is finished.
Actions

Partial.ly actions

Partial.ly gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create a Payment Plan

Action

In Zapier“Create a new payment plan, optionally sending a request to the customer to open the plan”

Sets up a new plan in Partial.ly from three required values: the Offer ID that defines the terms, the plan amount and the customer email.

When to use it
a sale closes in your checkout or CRM and you want the instalments ready without retyping anything.
Watch out
the plan request email only goes out if you switch on Send customer plan request.
2

Update a Payment Plan

Action

In Zapier“Update an existing payment plan”

Changes a plan that already exists. The only required value is the Payment Plan ID, so an earlier step has to carry it.

When to use it
a trigger on that same plan started the Zap, or Find a Payment Plan located it just before.
Watch out
the Zapier page does not list which parts of a plan you can change, so open the action in the editor to see the fields it offers.
Searches

Partial.ly search

1 search step looks for data that already exists in Partial.ly, so a later step can use it.

A search step sits under the SEARCH heading at the bottom of the Action event list. Three settings decide what happens when the result is not the one you expected.

1

Find a Payment Plan

Search

In Zapier“Search for a payment plan by ID.”

Looks up one existing plan by its ID and hands its details to the steps that follow.

When to use it
another app stored the plan ID, a support ticket for example, and you need the current state of that plan before acting on it.
Watch out
it searches by ID only; a customer name or email will not find anything, and adding it makes the Zap multi-step.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there. Switched on, the Zap goes on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create. Partial.ly offers no find-or-create variant, so you will not use it here.
  3. If multiple search results are found?
    Keep the first match (the default), stop the Zap, or pass every match to the next steps at once.
When it breaks

When a Partial.ly Zap breaks

Zapier links no help article to Partial.ly, so the known failure points are the general ones.

None of them is specific to payment plans, but each one costs money or data when you are dealing with instalments. If a Zap stops behaving, Zapier troubleshooting is the place to start.

  • No catch-up on old plans

    A Zap only reacts to what happens after you switch it on. Plans opened or payments failed before that never reach it; moving that backlog is a separate job.

  • A Zap that sets itself off

    If the action writes back into what the trigger watches, the Zap can start itself again and again and burn through your task count fast.

  • Bulk changes held back

    A sudden flood of events, after a bulk import or a migration, can be held back by Zapier's flood protection instead of running all at once.

  • Missing Offer ID

    Create a Payment Plan fails without an Offer ID, a plan amount or a customer email. A failed action costs no task, but the plan is not created either.
Need help

Need help automating Partial.ly with Zapier?

A person reads every message.

FAQ

Partial.ly Zapier integration: FAQ

01Is the Partial.ly Zapier integration free?
Yes. Partial.ly is not reserved for paid plans, so it works on the free Zapier plan. That plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger and one action. Add a filter, a second action or Find a Payment Plan, the Zap becomes multi-step and needs a paid plan. Your Partial.ly subscription is a separate matter that this page does not cover.
02How many Zapier tasks does a Partial.ly Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap built on Payment Succeeded with one action uses one task per payment; with three actions it uses three per payment. An action that fails is not counted. Watching for new events costs nothing either. The busiest triggers are usually the payment ones, so count your monthly payments before you pick a plan. A Zap on Payment Plan Paid fires once per plan, so it stays far cheaper.
03Does Partial.ly trigger Zaps in real time?
Yes. All 8 Partial.ly triggers are instant: Partial.ly tells Zapier when the event happens, and the Zap starts right away. The polling intervals of the plans, 15 minutes on Free down to 1 minute on Team and Enterprise, only apply to polling triggers, and Partial.ly has none. In the editor, a Zap built on an instant trigger shows a lightning bolt. That is the key point on a free plan: no 15-minute wait on any Partial.ly event.
04What does connecting Partial.ly to Zapier require?
A Partial.ly account, and access to any plan you did not create yourself but want the Zap to touch. In Zapier you open Apps, click + Add connection, search for Partial.ly, click Add connection, sign in to Partial.ly in the tab that opens and grant access. For Create a Payment Plan, you also need an offer already set up in Partial.ly, because the action requires its Offer ID. Once linked, the connection is reused by every Zap you build after that.
05Why does Payment Plan Opened fire for a plan that already existed?
Because that trigger covers two cases: a plan opened for the first time, and an existing plan opened again, for example a defaulted plan that is reopened. A welcome Zap built on it can therefore reach a returning customer a second time. Word the message so it reads well in both cases. Telling the two apart with a filter makes the Zap multi-step, which needs a paid plan. Payment Plan Defaulted, by contrast, fires only after several failed payments on the same plan.
06What if the Partial.ly operation you need is not there?
Then Zapier cannot do it for Partial.ly today. The editor offers 8 triggers, 2 actions (Create a Payment Plan and Update a Payment Plan) and 1 search, Find a Payment Plan, which works by ID only. Deleting a plan or refunding a payment is not on the list. That step stays a manual one inside Partial.ly, or it calls for a different tool. Check the editor before you build around a missing step.
07Zapier, Make or n8n for Partial.ly?
Decide on criteria, not on a ranking. Zapier gives Partial.ly 8 instant triggers, 2 actions and 1 search, and a two-step Zap runs on the free plan with 100 tasks a month. Before choosing another tool, check that it offers the same Partial.ly events, how it counts each run, and whether your Zaps would need filters or several actions, which on Zapier means a paid plan. Whichever tool you pick, test it on a real plan before you rely on it.
Same platform

Other docs you might need on this stack.

Browse all integrations