- Home
- Resources
- Integrations
- Parallax
Parallax Zapier integrationAutomate Parallax with Zapier.
Parallax Zapier integration: 6 triggers, 1 action, no search step. Parallax, the resourcing and forecasting tool that flags capacity, revenue and margin risk early, tells Zapier the moment a project offering or one of its roles is created, changed or deleted. Free plan included.
Beta app Zapier still marks this integration as beta.
Verified Trustpilot reviews · AI, automation & growth agency
What the Parallax Zapier integration actually does
The Parallax Zapier integration connects Parallax, a planning tool that helps you see capacity, revenue and margin trouble coming, to Zapier, a service that runs automations between apps. Parallax reports changes to its project offerings and their roles, and accepts one write: an outside reference stored on an offering.
Three outcomes teams build with it. Projects that open themselves in the delivery tool: New Project Offering starts the Zap, an Asana project is created, and Add External ID to Project Offering writes the Asana reference back onto the offering, so both records point at each other. Staffing that follows the plan: New Project Offering Role, Updated Project Offering Role and Deleted Project Offering Role tell your team chat or your hiring tracker each time a role is added, changed or dropped. A clean trail of changes: Updated Project Offering and Deleted Project Offering log every edit and removal in a sheet that finance can read without opening Parallax.
What Zapier does not do here. All six triggers are about offerings and their roles: nothing fires on people, capacity or forecasts. The single action only tags an offering with an outside ID; it cannot create, edit or delete an offering or a role. There is no search step, so a Zap cannot look an offering up on its own. And Parallax is listed as a beta app on Zapier, so its operations may still move.
Zapier words you will meet on this page
Seven terms, one line each, so the notes below read without detours.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap, here a change to a Parallax offering or role. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like a project in Asana.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Instant vs polling
- An instant trigger is reported by the app the moment it happens; a polling one is checked by Zapier on a timer. All of Parallax's are instant.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
What a Parallax Zap really costs
Parallax is not reserved for paid plans on Zapier, so it works from the free plan. Its triggers never cost a task, and since all six are instant, the plan's check interval never slows them down.
- Tasks on the free plan100 per month
- Zaps on the free planUnlimited
- Steps on the free plan1 trigger + 1 action
- Delay on Parallax triggersNone, all instant
You pay in tasks: each action that succeeds counts once, and one that fails is not counted. A Zap that posts each new role to your team chat spends one task per role. The Asana round trip above has two actions, the Asana project and Add External ID to Project Offering, so it spends two tasks per offering. It is also multi-step, and the free plan stops at one trigger and one action, so it needs a paid plan.
Connect your Parallax account to Zapier
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. A connection is your Parallax account linked to Zapier once, then reused by every step that uses Parallax.
- 02
Pick Parallax
In the dialog that opens, type Parallax in the search box and select it in the results. Then click Add connection, and Zapier opens a new tab for the sign-in.
- 03
Sign in and grant access
Sign in to Parallax in that tab and allow Zapier to use the account. You need a Parallax account, plus read or write rights on any project you do not own and want the Zap to touch.
Your first Zap: open an Asana project for each new offering
GoalEvery new project offering in Parallax gets its Asana project, and the offering keeps the Asana reference.
- 01
Set the trigger
In the Build step, pick Parallax and New Project Offering, then your connection. This instant event starts each run, with no waiting on any plan.
- 02
Test it on a real offering
Run the trigger test. Zapier brings back the three most recent items of the account, and you pick one, so the mapping in the next steps uses a real offering.
- 03
Create the Asana project
Add the Asana action that creates a project and map the offering's name into it. Asana then hands back the identifier of the project it just made.
- 04
Tag the offering
Add Add External ID to Project Offering. Map Project ID and Offering ID from the trigger, and External ID from the Asana step. Two actions make this a multi-step Zap, on a paid plan.
- 05
Test each step, then publish
Run each action once and check the tag on the offering in Parallax. Then click Publish. The Zapier training covers mapping between steps in depth.
Parallax triggers on Zapier
6 events start a Zap when something happens in Parallax, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.
New Project Offering
Instant triggerIn Zapier“Triggers when a new project offering is created.”
Fires when someone creates a project offering in Parallax. It is the start of most useful flows, because a new offering usually means work to set up in other tools.
Deleted Project Offering
Instant triggerIn Zapier“Triggers when a project offering is deleted.”
Reports the removal of a project offering. This is the signal to clean up whatever the offering had spawned elsewhere, before stale projects pile up in your delivery tools.
Updated Project Offering
Instant triggerIn Zapier“Triggers when a project offering is modified.”
Any change made to an existing project offering starts the Zap. Use it to keep other tools in step with what the planning team edits in Parallax.
New Project Offering Role
Instant triggerIn Zapier“Triggers when a new project offering role is created.”
Starts the Zap when a role is added to a project offering, the moment the plan says a new profile is needed on that work.
Deleted Project Offering Role
Instant triggerIn Zapier“Triggers when a project offering role is deleted.”
Tells Zapier that a role was removed from an offering, which often means a profile is no longer needed on that work.
Updated Project Offering Role
Instant triggerIn Zapier“Triggers when a project offering role is modified.”
Reacts to edits on an existing role of an offering, so any change in what the plan asks of that role reaches the people who staff it.
The Parallax action on Zapier
Parallax gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add External ID to Project Offering
ActionIn Zapier“Associates a custom external identifier (e.g. an Asana project ID) with a project offering, so the offering can be correlated back to a record in an external system.”
Stores the identifier of an outside record, an Asana project for instance, on a Parallax project offering. Later, anyone can trace the offering back to that record.
px_, which Parallax reserves, and may not contain a slash. Clean the value before it reaches this step.When a Parallax Zap breaks
Zapier ties no help article to Parallax, so the traps below are the general ones, read through what this app can and cannot do.
Instant triggers remove the waiting, not the other surprises. Read these cases first, then Zapier troubleshooting if a run still fails.
Existing offerings are not picked up
A Zap only reacts to what happens after you switch it on. Offerings and roles created before are ignored, and bringing that backlog over is a separate job.A Zap that sets itself off
A Zap that writes into the very place its own trigger watches sets itself off again and again. Tagging an offering from a Zap that watches offering updates is the case to test.A bulk import gets held back
Creating many offerings or roles at once, after an import or a migration, sends a huge batch to the trigger. Zapier's flood protection can hold it back.The External ID is refused
An External ID that starts with px_ or contains a slash breaks the rule of the field. Strip or reformat the value in an earlier step.
Need help automating Parallax with Zapier?
A person reads every message.



