Pixifi Zapier integrationAutomate Pixifi with Zapier.
The Pixifi Zapier integration gives you 25 triggers, 12 actions and 4 searches. 24 of those triggers report to Zapier on their own, so a signed contract or a paid invoice can start work in another tool without waiting for a check, even on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Pixifi Zapier integration does for you
It links your Pixifi account to Zapier, so what happens in your studio's back office (a lead coming in, a proposal accepted, an invoice paid) can start a Zap: an automation made of one trigger, the event that starts it, and one or more actions, the steps that do the work for you.
Three results people usually build first. A paid invoice turns into a to-do: Invoice Fully Paid starts the Zap and Create Task puts the delivery work on someone's list. A form filled on your website turns into a Pixifi lead with Create Lead, ready for your usual follow-up. And an accepted proposal opens the job file, with Proposal Accepted followed by Create Project.
The plan question is simpler here than on most apps. 24 of the 25 triggers are instant: Pixifi reports the event itself, so the Zap starts without waiting, free plan included. Only Event Start works by polling, which means Zapier checks on a timer set by your plan, every 15 minutes on the free one.
What Zapier does not do for Pixifi: there is no delete action, and nothing edits an existing client, event or invoice. The only changes it can make to existing records are the two status switches, for events and for leads. A Zap also never reaches back to records that existed before you switched it on. Still choosing a tool? Read Make vs Zapier first.
Zapier words, in plain English
Eight terms come back all over this page. One line each; after that, the page uses them as they are.
- Zap
- Your automation on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The Pixifi event that starts the Zap, such as a new lead or a payment marked paid. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes something for you, like creating a client or a task in Pixifi.
- Task
- The unit Zapier bills. One task is one action that completed successfully; the allowance on your plan is a count of those.
- Polling vs instant
- Polling: Zapier asks Pixifi for new items on a timer. Instant: Pixifi calls Zapier itself when the event happens, no waiting.
- Filter
- A step that lets the Zap carry on only when what arrived matches the condition you set, and stops it otherwise.
- Search step
- A step that looks up something already in Pixifi, a client or a staff member, so the steps after it can reuse what it found.
- Connection
- Your Pixifi account linked to Zapier once, then reused by every step that touches Pixifi, in every Zap you build.
What it really costs
Zapier does not reserve Pixifi for paid plans: it works on the free plan. What you spend is tasks.
- Paid plan required for PixifiNo
- Free plan tasks100 a month
- Free plan Zap sizeTwo steps: one trigger, one action
- Instant triggers24 of 25
The trigger never costs a task, and neither do Zapier's checks for new data. Each action that succeeds counts once, so a three-action Zap uses three times what a one-action Zap uses. A failed action is not counted. The free plan gives 100 tasks a month but only two-step Zaps. Add a filter, a search or a second action and the Zap turns multi-step, which needs a paid plan. The interval grid only matters for Event Start.
Connect Pixifi to Zapier in three steps
- 01
Open your connections
Before you start, have a Pixifi account, plus read or write access on anything you don't own yourself but want the Zap to touch. In Zapier, open the Apps page of your account and click + Add connection.
- 02
Pick Pixifi
In the dialog, search for Pixifi by name and select it in the results. Then click Add connection to start linking the two accounts. The sign-in itself comes in the next step.
- 03
Sign in and grant access
Sign in to Pixifi in the tab that opens, then grant Zapier access to the account. From then on, every step that uses Pixifi reuses this connection, in every Zap you build.
Your first Zap: a paid invoice becomes a to-do
GoalEach time an invoice is fully paid in Pixifi and matches your rule, a Pixifi task (the to-do, not a Zapier billing task) is created for the delivery work.
- 01
Build the Zap
Create a Zap and pick Pixifi as the app that starts it, with Invoice Fully Paid as the event. Choose the Pixifi connection you set up above.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real paid invoice, not an empty shell.
- 03
Add the filter
Click the plus icon, choose Filter, and fill the three boxes: the field to look at, the rule, the value. A text rule only works on text, a number rule on numbers. This step makes the Zap multi-step.
- 04
Add Create Task
Add Pixifi again as the action app and pick Create Task. Two fields are required, Task Title and Task Due Date: fill them from the invoice the test brought back.
- 05
Test the action
Run the step once and check the result in Pixifi before going further. Each successful run of this action is one task on your Zapier plan.
- 06
Publish
Click Publish to switch the Zap on. Only invoices paid after that moment will start it. Prefer to learn this with someone? See the Zapier training.
Pixifi triggers: what starts a Zap
25 events start a Zap when something happens in Pixifi, and 24 of them are instant: the app calls Zapier straight away, whatever your plan.
Contract Signed and Accepted
Instant triggerIn Zapier“Triggers when a Contract is signed and Accepted.”
A client signs, the contract shows as accepted in Pixifi, and Zapier is told. Of all the booking signals in the app, this is the firmest one: the paperwork is done.
Event Workflow Custom Trigger
Instant triggerIn Zapier“Triggers when an Event Workflow Phase Action or Automatic Action has been triggered in Pixifi.”
Your event workflows already run phase actions and automatic actions. This trigger lets one of those steps hand off to Zapier, so a precise point of the workflow can reach tools Pixifi does not talk to.
Lead Workflow Custom Trigger
Instant triggerIn Zapier“Triggers when a Lead Workflow Phase Action or Automatic Action has been triggered in Pixifi.”
Sales follow-up lives in your lead workflows. With this one, a phase action or an automatic action inside a lead workflow becomes the starting point of a Zap.
Product Workflow Custom Trigger
Instant triggerIn Zapier“Triggers when a Product Workflow Phase Action or Automatic Action has been triggered in Pixifi.”
Products such as albums or prints follow workflows of their own, apart from events and leads. Here, an action fired by a product workflow, phase or automatic, sends its signal to Zapier.
Project Workflow Custom Trigger
Instant triggerIn Zapier“Triggers when a Project Workflow Phase Action or Automatic Action has been triggered in Pixifi.”
Not every job is a dated event. For work tracked as a project, this trigger follows the project workflows and reacts when one of their phase actions or automatic actions runs.
Event Start
Polling triggerIn Zapier“Triggers a specified time before an Event starts.”
The only reminder-style trigger in the list: it starts the Zap a set time before an event begins, a delay you count in hours or in days.
Event Switches Status
Instant triggerIn Zapier“Triggers when the status of an Event is changed.”
Every time an event moves to another status in Pixifi, this trigger picks up the change and passes the event to Zapier, whoever made the switch.
Invoice Fully Paid
Instant triggerIn Zapier“Triggers when an Invoice is marked as "PAID" in Pixifi (either manually or automatically by checkout).”
When an invoice reaches “PAID” in Pixifi, whether someone marked it by hand or the checkout did it, Zapier hears about it and the Zap can move on.
Lead Converted
Instant triggerIn Zapier“Triggers when a Lead is Converted into a new Client + (Event or Project)”
A lead that becomes a client brings two records into Pixifi at once: a new client, plus an event or a project. This trigger fires at that conversion.
Lead Switches Status
Instant triggerIn Zapier“Triggers when the status of a Lead is changed.”
Your pipeline moves when a lead changes status, and this trigger follows those moves one by one, from first inquiry to the last stage you use.
New Client
Instant triggerIn Zapier“Triggers when a new Client is created in Pixifi.”
Each client record added to Pixifi is passed to Zapier with this trigger, which makes it the natural source for any list of customers you keep elsewhere.
New Event
Instant triggerIn Zapier“Triggers when a New Event is Scheduled in Pixifi.”
Scheduling a new event in Pixifi, a wedding, a portrait session, a corporate shoot, is what this one listens for, and the event goes straight to the Zap.
Expense Is Created
Instant triggerIn Zapier“Triggers when an Expense is created in Pixifi.”
Costs logged in Pixifi do not have to stay there: each expense created in the app can feed a Zap and travel to the tool your accountant actually reads.
New Invoice
Instant triggerIn Zapier“Triggers when a New Invoice is sent in Pixifi. (invoices that are marked as in Draft won't be sent).”
Here the signal is an invoice going out: when Pixifi sends a new invoice to a client, the Zap starts with that invoice in hand.
New Lead
Instant triggerIn Zapier“Triggers when a new Lead is created in Pixifi.”
Inquiries are the top of your funnel, and every lead created in Pixifi reaches Zapier through this trigger, ready for whatever comes next.
New Project
Instant triggerIn Zapier“Triggers when a New Project is created in Pixifi.”
Projects are the side of Pixifi that is not tied to one event date, and each one created there opens a Zap run through this trigger.
New Task
Instant triggerIn Zapier“Triggers when a New Task is added/assigned in Pixifi.”
Tasks added or assigned in Pixifi start the Zap with this trigger, which is handy when your team lives in another to-do app.
Payment Is Paid
Instant triggerIn Zapier“Triggers when a Payment is marked as "PAID" in Pixifi (either manually or automatically by checkout).”
Each payment, rather than the whole invoice, is what this trigger watches: when one is marked “PAID”, by hand or by checkout, it fires.
Product Switches Status
Instant triggerIn Zapier“Triggers when the status of a Product is changed.”
Products carry statuses of their own in Pixifi, and a change of status there is what wakes this trigger up.
Project Switches Status
Instant triggerIn Zapier“Triggers when the status of a Project is changed.”
Follow your projects through their stages: whenever one changes status in Pixifi, Zapier gets the project with its new status.
Proposal Accepted
Instant triggerIn Zapier“Triggers when a Proposal is accepted.”
The yes you were waiting for: when a client accepts a proposal, this trigger starts the Zap with the accepted proposal.
Proposal Sent
Instant triggerIn Zapier“Triggers when a Proposal is sent.”
Earlier in the sales cycle, this one reacts when a proposal leaves Pixifi for a client, before any answer comes back.
Questionnaire Answered
Instant triggerIn Zapier“Triggers when a Questionnaire is filled out completely and submitted.”
A questionnaire only counts once the client has filled in every part and submitted it; at that point this trigger passes the submission to Zapier.
System Notification
Instant triggerIn Zapier“Triggers when a System Notification is generated in Pixifi.”
Pixifi generates system notifications of its own, and this trigger turns each of them into a Zap run you can send anywhere.
Task Completed
Instant triggerIn Zapier“Triggers when a Task is marked as completed in Pixifi.”
Ticking a task off in Pixifi can set off what comes next: this trigger fires when a task is marked completed.
Pixifi actions: what a Zap can do
Pixifi gives you 12 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Client
ActionIn Zapier“This will create a new Client in Pixifi.”
Adds a fresh client record to Pixifi from whatever the trigger brought in.
Create Event
ActionIn Zapier“This will create a new Event in Pixifi.”
Puts a new event on the Pixifi calendar from data held elsewhere.
Switch Event Status
ActionIn Zapier“This will Switch the status of an Event in Pixifi with the new Status passed in.”
Moves an existing event to the status you pass in, one of the two ways a Zap can change an existing record.
Create Expense
ActionIn Zapier“This will create a new Expense in Pixifi.”
Logs an expense in Pixifi from a receipt or a purchase recorded in another app.
Create Invoice
ActionIn Zapier“This will create a new Invoice in Pixifi.”
Builds an invoice in Pixifi, with a line item, from data coming from another tool.
Attach Document to Lead
ActionIn Zapier“This will create a new Document and attach it to a Lead in Pixifi.”
Creates a document and hangs it on an existing lead, from a link to the file.
Create Lead
ActionIn Zapier“This will create a new Lead in Pixifi.”
Turns an inquiry captured outside Pixifi into a lead, so it enters your usual lead workflow.
Create "Project" Type Lead
ActionIn Zapier“This will create a new Lead in Pixifi, but instead of having Event data, it will contain Project data.”
Works like Create Lead, except the new lead carries project data instead of event data.
Switch Lead Status
ActionIn Zapier“This will Switch the status of a Lead in Pixifi with the new Status passed in.”
Changes the status of an existing lead, so your pipeline reflects what happened outside Pixifi.
Create Payment
ActionIn Zapier“This will create a new Payment in Pixifi.”
Records a payment you received somewhere else, so Pixifi's books match your bank.
Create Project
ActionIn Zapier“This will create a new Project in Pixifi.”
Opens a project in Pixifi, the container for work not tied to one event.
Create Task
ActionIn Zapier“Creates a new Task.”
Drops a new to-do into Pixifi, with a title and a deadline.
Pixifi searches: reuse what already exists
4 search steps look for data that already exists in Pixifi, so a later step can use it.
A search step looks up a Pixifi record that already exists. In the editor, searches sit at the bottom of the Action event list, under SEARCH, and some action fields offer + Add search step to insert one for you. Whether a search wants an exact value or a close one is Pixifi's call, not Zapier's.
Find Client by ID
SearchIn Zapier“Find existing Clients from clientID.”
Fetches one client when you already hold its Pixifi identifier.
Find Client by Info
SearchFind or createIn Zapier“Find existing Client from client info (name, email), it will return back the first result found.”
Looks a client up by name or email and returns the first match it finds.
Find Event Type by Name
SearchIn Zapier“Find existing Event Type from Event Type Name.”
Turns an event type's name into the event type Pixifi expects.
Find Staff Member by Info
SearchIn Zapier“Find existing Staff Members from their personal info (name, email).”
Finds someone on your team from their name or email.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the steps that depend on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking it turns the search into a find-or-create: the setting above disappears and the step asks for what it needs to create the missing record.
- If multiple search results are found?Three ways out when several records match: keep the first one (the default), stop the Zap, or hand all of them on at once.
When a Pixifi Zap breaks
Zapier attaches no help article to Pixifi, so the traps below are the general ones, applied to this app.
Four situations to know before you publish. If a Zap still misbehaves after that, go through Zapier troubleshooting.
No catch-up on old records
A Zap only reacts to what happens after you switch it on. Clients, leads or invoices already in Pixifi are never picked up; moving them is a separate job.A Zap that feeds itself
A Zap on New Task that runs Create Task, or New Lead with Create Lead, sets itself off again and again and burns through your task count fast.Bulk imports held back
Import a large batch of clients or leads and a trigger may return a huge pile at once. Zapier's flood protection can hold that batch back.Event Start never doubles up
On Event Start, the only polling trigger here, Zapier keeps track of what it has already seen, so the same event does not start the Zap twice.
Need help automating Pixifi with Zapier?
A person reads every message.



