Resources · Zapier integration

PHC GO Zapier integrationAutomate PHC GO with Zapier.

The PHC GO Zapier integration gives you 14 triggers, 11 actions and 2 searches. Every trigger is instant, the app runs on the free plan, and the real traps hide in the required fields and in the two-step cap of that free plan.

See the 27 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the PHC GO Zapier integration actually does

A Zap is the automation you build on Zapier: one event that starts it, then one or more steps that run each time that event happens. With PHC GO, the event can be a customer, an article, an order, a task or a calendar event changing in the software, and the steps can write customers, articles, orders, invoices and tasks back into it.

Three results come up again and again. A follow-up that writes itself: New Order starts the Zap and Create Tasks drops a to-do for the person who prepares the delivery. A billing trail without retyping: an order taken in another tool reaches PHC GO through Create Order or Create Invoice, with the document series picked once in the editor. A catalog that stays honest: Insert/ Update Article pushes every new or edited reference to the shop or the price sheet your sales team reads.

Now the limits. None of the 11 actions deletes anything: you can create, update and cancel an order, not erase a record. None of the 14 triggers watches invoices. No search offers a find-or-create variant, so a Zap cannot look for a customer and create it in the same step. And a Zap never picks up what existed before you switched it on.

This page reads PHC GO as Zapier lists it (implementation PhcGoCLIAPI@1.0.11, read on 14 October 2026). For a second opinion on the tool itself, there is the Zapier review, and the trade-offs with an open-source option are in n8n vs Zapier.

Vocabulary

The Zapier words you will meet on this page

Eight terms, plain English, one line each. They are used without a reminder after this.

Zap
Your automation on Zapier: 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 that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself when the event happens.
Filter
A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it otherwise.
Search step
A step that looks up something already stored in an app, so the steps after it can reuse what it found.
Connection
Your PHC GO account linked to Zapier once, then reused by every step of every Zap that touches PHC GO.
Cost

What a PHC GO Zap costs you

Zapier bills completed actions, not events. The trigger itself never costs a task, and an action that fails is not counted.

  • Free plan100 tasks a month, unlimited Zaps
  • Steps on the free plan2: one trigger, one action
  • Instant triggers14 out of 14
  • Reserved for paid plansNo

PHC GO is not reserved for paid plans, so it runs on the free plan: 100 tasks a month and as many Zaps as you like, but each Zap stops at two steps, one trigger and one action. Add a second action, a filter or a search and the Zap becomes multi-step, which needs a paid plan. A three-action Zap uses three times the tasks of a one-action Zap. The polling grid below is the general rule; it does not touch PHC GO, whose 14 triggers are all instant.

Connect

Connect your PHC GO account

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. Type PHC GO in the dialog and pick it from the list. You need a PHC GO account before you start.

  2. 02

    Sign in to PHC GO

    Click Add connection. A new tab opens on PHC GO: sign in with the account whose data the Zaps will read and write. The connection belongs to that account, so pick it on purpose rather than the first login at hand.

  3. 03

    Grant access

    Allow Zapier to reach the account. If your Zaps will touch customers, orders or articles that someone else owns, that account needs read or write rights on them, or the steps will have nothing to work with.

First Zap

Your first Zap: a task for every new order worth preparing

GoalWhen an order lands in PHC GO and passes your condition, a task appears in PHC GO for the person who prepares it.

  1. 01

    Pick the trigger

    Build the Zap: choose PHC GO as the app that starts it and New Order as the event. Select the PHC GO connection you created above.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent orders of the connected account, so pick a real one: every later step maps its fields from it.

  3. 03

    Add the filter

    Add a Filter step from the plus icon. Choose a field of the order you just tested, the rule, then the value. A text rule only works on text, a number rule only on numbers.

  4. 04

    Add the action

    Add PHC GO again with Create Tasks. Summary, Start date, End date and Description are required: map them from the order, or type fixed wording for the summary.

  5. 05

    Test, then publish

    Test the action and open the task in PHC GO to read what came back. Then publish the Zap to switch it on. With a filter this Zap has three steps, so it needs a paid plan.

Triggers

The 14 PHC GO triggers

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

1

Insert/ Update Customer

Instant trigger

In Zapier“Triggers when a new customer is created or updated in the PHC GO software.”

Fires on two events at once: a customer that appears in PHC GO for the first time, and an existing one that someone edits. One Zap is enough to keep a second copy of your customer file in line with the accounting side.

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 mailing list or a shared sheet has to follow every customer change, new or old, without two separate Zaps.
Watch out
paired with Create/ Update Customer on the same record, each write starts the Zap again.
2

Delete Article

Instant trigger

In Zapier“Triggers when a new article/ service/ product is deleted in the PHC GO software.”

Reacts when an article, a service or a product is removed from PHC GO. The Zap receives the removal and can clean up every other place where that item was still listed.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your online catalog or price list lives in another tool and must stop showing what the back office deleted.
Watch out
deleting and deactivating are separate events here; an item set to inactive goes through Inactive Article.
3

Delete Calendar Event

Instant trigger

In Zapier“Triggers when a new calendar event is deleted in the PHC GO software.”

Starts the Zap when someone removes an event from the PHC GO calendar, so a cancelled appointment does not live on in another diary or on a planning board.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your team mirrors PHC GO appointments into a shared calendar and a cancellation has to follow there too.
Watch out
it only sees removals; a moved or created event belongs to Insert/ Update Calendar Event.
4

Delete Customer

Instant trigger

In Zapier“Triggers when a customer is deleted from the PHC GO software.”

Picks up a customer erased from PHC GO. Use it to close the loop in the tools that still hold that contact: a newsletter list, a support desk, a shared address book.

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 contact removed from billing should stop receiving your campaigns without anyone thinking about it.
Watch out
a customer switched to inactive is still in PHC GO, so this trigger stays silent; Inactive Customer handles that case.
5

Insert/ Update Calendar Event

Instant trigger

In Zapier“Triggers when a new calendar event is created in the PHC GO software.”

Wakes the Zap when an event lands in the PHC GO calendar. Its name promises creations and updates, while the app's own description only mentions new events.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
someone books a visit or a call in PHC GO and the person concerned should hear about it in the tool they actually check.
Watch out
before trusting it with edits, change a test event and check that the Zap really starts.
6

New Order

Instant trigger

In Zapier“Triggers when a new order/ internal dossiers is created in the PHC GO software.”

Opens the Zap each time an order, or what PHC GO calls an internal dossier, is created. It is the natural starting point for everything that follows a sale: preparation, follow-up, alerts to the right person.

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 warehouse or the field team needs a to-do for each new order without logging in to the accounting side.
Watch out
a Zap that also writes orders through Create Order can feed this trigger; keep the two apart.
7

Inactive Article

Instant trigger

In Zapier“Triggers when a product/ article it's set to inactive in the PHC GO software.”

Catches a product or article that someone switches to inactive in PHC GO. The item still exists; it just stops being offered, and the other tools can follow suit without losing its history.

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 discontinued product must leave the shop window or the sales team's price sheet, while staying in past orders.
Watch out
a real deletion fires Delete Article instead, so build one Zap per case if both matter.
8

Inactive Customer

Instant trigger

In Zapier“Triggers when a customer/ subscriber it's set to inactive in the PHC GO software.”

Goes off when a customer, or a subscriber, is marked inactive in PHC GO. The record stays in the software but the relationship is on pause, and that pause can travel to the tools around it.

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 subscriber who stops should leave the onboarding sequence or the account manager's call list.
Watch out
it reacts to this status only, not to any other customer edit; Update Customer covers those.
9

Insert Article

Instant trigger

In Zapier“Triggers when a new article/ service/ product is created in the PHC GO software.”

Only a brand-new article, service or product sets this one off. Edits to existing items leave it quiet, which keeps the Zap focused on launches and nothing else.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
every new reference should create a task for whoever writes the product sheet or checks the price.
Watch out
Insert/ Update Article also fires on creations; running both doubles the tasks your actions spend.
10

Insert Customer

Instant trigger

In Zapier“Triggers when a new customer is created in the PHC GO software.”

Starts on the creation of a customer in PHC GO, and on nothing else. Later corrections to that record will not set it off, so whatever you build runs once per customer.

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 newly signed account should get a welcome email or a CRM entry once, not on every fix.
Watch out
customers that a Zap of yours writes through Create Customer fire it too; check what feeds PHC GO before publishing.
11

Insert Task

Instant trigger

In Zapier“Triggers when a new task is created in the PHC GO software.”

Listens for tasks created in PHC GO. Whoever adds one, the Zap can carry it to the place where your team actually reads its to-dos.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
tasks are logged in PHC GO for traceability, but the team works from a chat tool or a project board and never opens that screen.
Watch out
Create Tasks writes into the very place this trigger watches, so a Zap that starts here and ends there loops.
12

Insert/ Update Article

Instant trigger

In Zapier“Triggers when a new article/ service/ product is created or updated in the PHC GO software.”

Covers both sides of the catalog: an article, service or product that appears, and one that changes. A single Zap keeps a second catalog aligned with PHC GO.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your e-shop or the price sheet of the sales team must reflect each new reference and each edit made in PHC GO.
Watch out
the Create/ Update Article action writes into what this trigger watches, so never chain the two in one Zap.
13

Update Article

Instant trigger

In Zapier“Triggers when a new article/ service/ product is updated in the PHC GO software.”

Fires when an existing article, service or product is modified, and stays quiet on new ones. That narrow scope suits Zaps that only care about changes to what you already sell.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
price or description changes must reach a sales sheet, while launches are handled by a different Zap.
Watch out
with Insert/ Update Article running as well, one edit starts both Zaps and each spends its own tasks.
14

Update Customer

Instant trigger

In Zapier“Triggers when a new customer is updated in the PHC GO software.”

Reacts to an edit on a customer who already exists in PHC GO, whatever was changed in the record. New customers do not reach it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your CRM or mailing tool should never keep an outdated version of a customer that accounting has corrected.
Watch out
pointed at the same record, Create/ Update Customer makes the Zap set itself off again and again, and burns tasks fast.
Actions

The 11 PHC GO actions

PHC GO gives you 11 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Cancel Order

Action

In Zapier“This action allows to calcel orders in the integrated application.”

Cancels an existing order in PHC GO. It needs the document type, the document number and a reason for the cancellation.

When to use it
a refund or a cancelled cart in another tool should close the matching order on the accounting side.
Watch out
the Zap must carry the order number from an earlier step; without it there is nothing to cancel.
2

Create Avenca

Action

In Zapier“This action allows to create "avencas" in the integrated application.”

Sets up an avença in PHC GO: a recurring agreement that issues invoices on the recurrence you choose. Summary, issue date, recurrence and customer name are required.

When to use it
a signed subscription or retainer elsewhere should start its billing cycle in PHC GO.
Watch out
the summary serves as the identifier of the avença, so make it unique and readable.
3

Create Customer

Action

In Zapier“This action allows to create customer in the integrated application.”

Adds a customer to PHC GO from whatever started the Zap. Only the name is required, so a form or a signup can feed it with very little.

When to use it
new leads from a web form should exist in PHC GO before anyone invoices them.
Watch out
it always creates; if the customer may already exist, Create/ Update Customer avoids duplicates.
4

Create Invoice

Action

In Zapier“This action allows to create invoices/ paid orders in the integrated application.”

Issues an invoice, or a paid order, in PHC GO. It asks for the customer name, an option for what happens at issue, the document type, the product reference, the unit price and the quantity.

When to use it
a paid online order should leave a proper invoice in the accounting software.
Watch out
an optional box can delete tax numbers that are invalid on newly created customers; decide on it deliberately.
5

Create Order

Action

In Zapier“This action allows to create orders in the integrated application.”

Creates an order, an internal dossier in PHC GO terms, for a customer and a product. Customer, document type, reference, unit price and quantity are required.

When to use it
orders taken in a shop or a sales app must reach PHC GO without being retyped.
Watch out
the document type is a series you pick in PHC GO; choose it once, carefully, in the editor.
6

Create Article

Action

In Zapier“This action allows to create article/ service/ product in the integrated application.”

Creates an article, a service or a product in PHC GO. Reference and Designation are required; tax settings per price and the service flag are optional.

When to use it
new products are drafted in a spreadsheet or a shop back office and must exist in the accounting catalog too.
Watch out
the reference identifies the item, so map a stable code such as a SKU, not a name that may change.
7

Create Records

Action

In Zapier“This action allows to create new records, in native and framework entities, from the integrated application.”

Writes a new record in a native or framework entity of PHC GO. You choose the entity first, and the rest follows from that choice.

When to use it
what you want to create is not a customer, an article, an order, an invoice, a task or an event.
Watch out
this is the advanced route; test it on a harmless entity before pointing it at live data.
8

Create Tasks

Action

In Zapier“This action allows to create tasks in the PHC GO integrated application.”

Puts a task in PHC GO with a summary, a start date, an end date and a description, all four required.

When to use it
an order, a ticket or a form answer should turn into a dated to-do for someone in the team.
Watch out
map real dates from the earlier steps; an empty required date leaves the action with nothing valid to write.
9

Create/ Update Customer

Action

In Zapier“This action allows the creation or updating of customers in the integrated application”

Writes a customer into PHC GO, creating the record when it is missing and updating it otherwise. The name is the one required field.

When to use it
a CRM or a shop sends the same customers again and again, and PHC GO should hold one clean record each.
Watch out
do not start this Zap from a customer trigger of PHC GO, or it loops.
10

Create/ Update Article

Action

In Zapier“This action allows the creation or updating of article/ service/ product in the integrated application.”

Creates the article when its reference is unknown and updates it when it already exists. Reference is the only required field, with optional tax settings and a fixed-quantity option for components.

When to use it
a supplier feed or a product sheet is the master, and PHC GO should follow it without duplicates.
Watch out
never trigger it from an article trigger of PHC GO; each write fires the trigger again.
11

Create Event

Action

In Zapier“This action allows to create calendar Events in the integrated application.”

Books a calendar event in PHC GO. Title, date, start time, end time and the participant email are all required.

When to use it
a meeting booked through an online scheduler should appear in the PHC GO calendar of the person who will attend.
Watch out
the start and end times expect an hour and minutes format, so check how the earlier step hands them over.
Searches

The 2 PHC GO searches

2 search steps look for data that already exists in PHC GO, so a later step can use it.

Searches sit at the bottom of the action event list, under their own SEARCH heading. They hand what they find to the steps that follow. A Zap with a search is multi-step, so it needs a paid plan. PHC GO offers no find-or-create variant.

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 and skips the steps that relied on it. Switched on, the Zap goes on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Neither PHC GO search offers it, so a missing item has to be created by a separate action.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When a PHC GO Zap breaks

Zapier attaches no help article to PHC GO and lists no app-specific limit. What breaks comes from general Zapier rules, and PHC GO has a few ways to hit them.

  • Nothing from before the Zap

    A Zap only reacts to what happens after you switch it on. Customers and articles already in PHC GO are never picked up; moving them is a separate job.

  • The Zap that feeds itself

    Update Customer plus Create/ Update Customer, or Insert/ Update Article plus Create/ Update Article: the Zap writes where its trigger watches and burns tasks fast.

  • A bulk import held back

    Import a whole catalog into PHC GO and the article triggers return a huge batch at once. Zapier's flood protection can hold that batch back.

  • A filter that never passes

    Filter rules are typed: a text rule only reads text, a number rule only numbers. Pick the wrong one and no order ever reaches the action.
Need help

Need help automating PHC GO with Zapier?

A person reads every message.

FAQ

PHC GO and Zapier: the questions people ask

01Is the PHC GO Zapier integration free?
Yes. PHC GO is not one of the apps Zapier reserves for paid plans, so it works on the free plan. That plan gives you 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. Add a second action, a filter or a search, and the Zap becomes multi-step, which needs a paid plan. A scenario such as a new order that creates a task only for some orders already crosses that line, because the filter counts as a step.
02How many tasks does a PHC GO Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that starts on New Order and runs Create Tasks costs one task per order. Add Create Event as a second action and it costs two. An action that fails is not counted against your plan. Zapier also notes that a few apps and a few actions take more than one task when they complete, so read your plan's count after the first real runs rather than assuming.
03Do PHC GO triggers run in real time?
Yes. All 14 PHC GO triggers are instant: PHC GO reports the event to Zapier itself, so the Zap starts right away whatever your plan. The polling interval of the plans, 15 minutes on the free plan, does not apply to any of them. In the editor, a Zap built on one of these triggers shows a lightning bolt. The type comes from the app and cannot be changed from Zapier.
04What do you need to connect PHC GO to Zapier?
A PHC GO account, and read or write rights on any record you do not own but want the Zap to touch. From the Apps page of Zapier, click + Add connection, search PHC GO, click Add connection, sign in to PHC GO in the tab that opens and grant Zapier access. The connection is then reused by every Zap. Pick an account that can see the document series used by orders and invoices.
05Why does a PHC GO Zap keep starting on its own?
Because it writes into the place its trigger watches. Update Customer with Create/ Update Customer, Insert/ Update Article with Create/ Update Article, or Insert Task with Create Tasks all form a loop: the action changes PHC GO, PHC GO reports the change, and the Zap runs again. Each run spends tasks. Switch the Zap off, then rebuild it so the trigger and the action touch different kinds of records. Read the task count of your plan afterwards to see what the loop already spent.
06What if the PHC GO operation you need is not in Zapier?
Check the generic pair first. Create Records writes into any native or framework entity of PHC GO, and Search Records reads from one, so something without its own action may still be reachable that way. If neither fits, the operation simply is not offered by this integration: 27 operations are available, listed in full on this page. The remaining routes are doing that step in PHC GO itself or with a different automation tool.
07Zapier, Make or n8n for PHC GO?
It depends on three criteria rather than a ranking. First, the triggers: on Zapier all 14 PHC GO triggers are instant, so check whether the other tool covers the same events. Second, the operations: list the ones your scenario needs and look for each of them. Third, the cost model: Zapier bills each successful action, and its free plan stops at two steps, so a scenario with a filter or several actions means a paid plan.
Same platform

Other docs you might need on this stack.

Browse all integrations