Resources · Zapier integration

Platform.ly Zapier integrationAutomate Platform.ly with Zapier.

The Platform.ly Zapier integration gives you 4 triggers and 5 actions, all built around contacts, tags and segments. Every trigger is a polling one, there is no search step, and the app runs on the free plan. Here is what each one does and costs.

See the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Platform.ly Zapier integration actually does

Hooking Platform.ly up to Zapier lets something that happens to your contacts start work in another tool, and lets work done in another tool land on a contact. On the Platform.ly side, you get four things to watch (contacts, custom fields, segments, tags) and five things to do, all of them about a contact.

Three setups cover most of what people build with it. Leads that arrive already filed: a form or a checkout in another app starts the Zap, and Create Contact puts the person in the right Platform.ly project, so your own Platform.ly automations take it from there. Contacts sorted on arrival: New Contact starts the Zap, then Add Tag to Contact or Add Segment to Contact labels them. A team that hears about structure changes: New Tag, New Segment or New Custom Field starts a Zap that posts a line in the tool your team already reads.

Now the part the app page skips. None of the four triggers is instant, so nothing fires on the spot: Zapier checks on a timer. There is no search step either, which means a Zap cannot look up an existing contact by email before acting on it. And the tag and segment actions want a Contact ID, so that ID has to come from an earlier step, in practice the New Contact trigger. There is no action to delete a contact.

If you are weighing tools for the same job, there is a Platform.ly Make integration page, and a comparison at n8n vs Zapier.

Vocabulary

Zapier words, in plain English

Eight terms come back on every line of this page. One sentence each, then they are used as is.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or changes something for you, here mostly on a contact.
Task
The unit Zapier bills. One action that completes successfully is one task, and your plan is a monthly count of those.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what it has not seen.
Instant trigger
A trigger the app reports itself, the moment the event happens. Platform.ly has none: all four of its triggers are polling ones.
Filter
A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it quietly otherwise.
Connection
Your Platform.ly account linked to Zapier once, then reused by every step of every Zap that touches Platform.ly.
Cost

What a Platform.ly Zap really costs

Zapier counts tasks, not Zaps. The trigger is free, checking for new contacts is free, and only an action that goes through is billed.

  • Free plan100 tasks a month, unlimited two-step Zaps
  • Trigger checksNever billed, however often Zapier looks
  • Failed actionNot counted against your plan
  • Paid plan needed forA second action, a filter or a search

A Zap that tags each new contact spends one task per contact. Add a second action to drop that contact into a segment and the same contact now costs two tasks, because each successful action counts on its own. An action that fails is not counted. Platform.ly is not one of the apps Zapier keeps for paid plans, so it works on the free plan, but the free plan only builds two-step Zaps: one trigger, one action. A second action or a filter makes it a multi-step Zap, and that needs a paid plan.

Connect

Connect your Platform.ly account in 3 steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. You need a Platform.ly account, plus read or write access on anything you do not own and want a Zap to touch.

  2. 02

    Pick Platform.ly

    Type Platform.ly in the dialog, select it in the results, then click Add connection. A new tab opens on the Platform.ly side, where the rest of the connection happens.

  3. 03

    Sign in and allow access

    Sign in to Platform.ly in that tab and grant Zapier access to the account. The connection now shows on your Apps page, ready for every Zap that uses Platform.ly.

First Zap

Your first Zap: tag and segment every new contact

GoalEach new Platform.ly contact gets a tag and lands in a segment, with nobody clicking anything.

  1. 01

    Pick the trigger

    Start a new Zap, choose Platform.ly as the app and New Contact as the event, then select the Platform.ly connection you just made.

  2. 02

    Test it on a real contact

    Run the trigger test. Zapier brings back the three most recent contacts of the account, so pick one you recognise: the next steps are mapped on it.

  3. 03

    Add the tag

    Add Add Tag to Contact as the action. Map the Contact ID from the trigger, then enter one Tag ID, or several separated by commas.

  4. 04

    Add the segment

    Add Add Segment to Contact, reuse the same Contact ID and enter the Segment ID. Two actions make this a multi-step Zap, so a paid plan is required.

  5. 05

    Test, then publish

    Test each step once and read what came back. When the tag and segment show on the test contact, click Publish to switch the Zap on.

Triggers

The 4 Platform.ly triggers

4 events start a Zap when something happens in Platform.ly. Zapier checks for them at the interval your plan allows.

1

New Contact

Polling trigger

In Zapier“Triggers when a new contact is created.”

Starts a Zap each time a contact appears in your Platform.ly account, whichever way it got there. It is the trigger that feeds almost every other scenario, because it hands over the Contact ID the tag and segment actions need.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
you want every newcomer pushed to your CRM, your sheet or your sales channel without retyping.
Watch out
contacts created before the Zap was published are never picked up, and a Zap that creates Platform.ly contacts in the same project will set this trigger off again.
2

New Custom Field

Polling trigger

In Zapier“Triggers when a new custom field is created.”

Fires when someone adds a custom field to the account, the extra data slot you define on contacts. It reports a change in how your data is organised, not a change to a contact.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
several people edit the account and you want a record of every new field in a shared sheet, so forms and reports stay in sync.
Watch out
this does not fire when a contact's field value changes, only when a new field is created.
3

New Segment

Polling trigger

In Zapier“Triggers when a new segment is created.”

Kicks off a Zap whenever a new segment is created in Platform.ly. Segments are how you group contacts, so this tells you a new group exists, not who is in it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
your team needs the ID of each new segment to build Add Segment to Contact steps, and you want it posted where everyone can copy it.
Watch out
it reports the segment itself; contacts entering a segment later do not start this Zap.
4

New Tag

Polling trigger

In Zapier“Triggers when a new tag is created.”

Watches the list of tags and starts a Zap each time a new tag shows up in the account. Like New Segment, it is about your labels, not about the contacts wearing them.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
you keep a tag reference in a spreadsheet and want each new tag, with its ID, added to it for whoever builds Add Tag to Contact steps.
Watch out
tagging an existing contact with an existing tag does not fire it.
Actions

The 5 Platform.ly actions

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

1

Add Segment to Contact

Action

In Zapier“Add segment to contact.”

Places an existing contact into one segment, or several at once if you list the Segment IDs separated by commas.

When to use it
a purchase in your shop should move the buyer into a customers segment.
Watch out
it needs the Contact ID, and with no search step on this app, that ID must come from an earlier step.
2

Remove Segment From Contact

Action

In Zapier“Remove Segment from Contact.”

Takes a contact out of one or more segments, using the same comma-separated Segment IDs as the add action.

When to use it
a refund or a cancellation in your billing tool should pull the person out of an onboarding segment.
Watch out
the segment stays; only the link between that contact and that segment goes.
3

Add Tag to Contact

Action

In Zapier“Add tag to contact.”

Puts one tag on a contact, or several at once from a comma-separated list of Tag IDs. In many accounts, that tag is the very cue your own Platform.ly automations are waiting for before they start.

When to use it
a webinar registration elsewhere should label the attendee so the right sequence starts.
Watch out
the field takes Tag IDs and will not recognise a tag name, so keep a list of IDs at hand, which the New Tag trigger can build for you.
4

Create Contact

Action

In Zapier“Creates a new contact.”

Adds a brand new contact to a Platform.ly project, with the email address as the required field alongside the project.

When to use it
leads from a form tool or an ad platform should land in Platform.ly ready for your sequences.
Watch out
Platform.ly accepts only real, valid addresses, so a dummy sample email makes the test fail; test with a real one.
5

Update Contact

Action

In Zapier“Updates contact info.”

Changes the details of a contact that already exists, with the email address and the project as required fields.

When to use it
a customer edits their profile in your app and Platform.ly should carry the same information.
Watch out
the Project ID has to match the project of the connection; to update contacts in another project, connect another account.
When it breaks

When a Platform.ly Zap breaks

Zapier attaches no help article to Platform.ly, so the traps below come from the required fields of the app and from how every Zap behaves.

Most failures here are not outages. They are a test run on fake data, a project that does not match the connection, or a Zap that feeds itself. Read the cases before you publish, and keep Zapier troubleshooting at hand for the rest.

  • The test email is rejected

    Create Contact and Update Contact accept only real addresses. If the sample data holds a dummy email, type a real one, test, then map the field again.

  • The contact goes to the wrong project

    The Project ID must match the project chosen at connection time. Another project means another connected account, not another value in the field.

  • Old contacts never show up

    A Zap only reacts to what happens after it is switched on. Contacts already in Platform.ly are not picked up; moving them is a separate job.

  • The Zap keeps setting itself off

    New Contact feeding Create Contact in the same project is a loop: each new contact starts the Zap again and eats through your tasks.

  • A bulk import stalls the trigger

    After a large import, New Contact may suddenly return a huge batch, and Zapier's flood protection can hold it back.

  • No contact runs twice

    Zapier remembers what a polling trigger has already seen, so the same contact does not start the Zap a second time.
Need help

Need help automating Platform.ly with Zapier?

A person reads every message.

FAQ

Platform.ly Zapier integration: frequent questions

01Is the Platform.ly Zapier integration free?
Yes, as long as your Zap stays at two steps. Platform.ly is not reserved for paid plans, so the free plan can run a Zap with one Platform.ly trigger and one action, within 100 tasks a month and with a check every 15 minutes. The moment you add a second action, a filter or a search, the Zap becomes multi-step and needs a paid plan. Tagging and segmenting a new contact in the same Zap, for instance, already crosses that line.
02How many tasks does a Platform.ly Zap use?
One per successful action, nothing for the trigger. A Zap that creates a contact uses one task each time it runs. A Zap that adds a tag and then a segment uses two per contact, because each action that completes is counted on its own. Zapier checking Platform.ly for new contacts, tags or segments costs nothing, however often it looks, and an action that fails is not billed. On the free plan, that leaves 100 successful actions a month.
03Do Platform.ly triggers fire instantly?
No. All four Platform.ly triggers, New Contact, New Custom Field, New Segment and New Tag, are polling triggers. Zapier asks Platform.ly for new items at a fixed interval: every 15 minutes on the free plan, every 2 minutes on Professional, every minute on Team and Enterprise. This cannot be switched from the editor, because the type is set by the app. On a paid plan you can also run a check by hand from the editor while you build.
04What does it take to connect Platform.ly to Zapier?
A Platform.ly account you can sign in to, plus read or write access on anything you do not own and want a Zap to touch. The connection itself happens from the Apps page of Zapier: add a connection, pick Platform.ly, sign in in the tab that opens and grant access. Keep in mind which project you choose there, because Create Contact and Update Contact will only write into that project.
05Why does Create Contact fail during the test?
Usually because the email is not real. Platform.ly only accepts valid addresses that actually exist, and sample data passed along by an earlier step often holds a placeholder. Type a real address by hand in the Email field, run the test until it succeeds, then map the field from the earlier step again. The other usual cause is a Project ID that does not match the project set on the connection.
06What if the Platform.ly action you need is missing?
Then the Zapier catalogue does not cover it today. The visible list is 4 triggers and 5 actions, all about contacts, tags and segments, with no search step and no way to delete a contact. A workable route is often to let Platform.ly do the rest: a tag added by Zapier can start an automation inside Platform.ly itself. If the step truly has to sit outside Platform.ly, compare what the other automation tools expose for this app before building around the gap.
07Zapier, Make or n8n for Platform.ly?
Decide on criteria, not on a name. On Zapier, check that the 4 triggers and 5 actions cover your scenario, that polling every 15 minutes on the free plan is fast enough, and that your Zap fits in two steps or justifies a paid plan. Then put the same three questions to the other tools: which Platform.ly operations they expose, how quickly they pick up a new contact, and what a run costs. The answer depends on your volume and on who maintains the Zap.
Same platform

Other docs you might need on this stack.

Browse all integrations