Look up every FieldPulse Zapier trigger and action, the fields each one sends or needs, and an example Zap that emails your office when a job is completed.
Listen to this pageabout 5 min
Who uses this: Admins. Availability: All regions; requires a Zapier account.
The FieldPulse Zapier integration has 6 triggers and 7 actions. A trigger is the event in FieldPulse that starts a Zap. An action is what FieldPulse does when a Zap runs. This page lists every trigger and action, the data each one sends or needs, and a complete example Zap.
The New Customer trigger starts a Zap when a customer is added in FieldPulse. It sends the following fields to Zapier: ID, Company Id, First Name, Last Name, Middle Name, Email, Phone, City, State, Zip Code, Postal Code, Location, Address, Tags, and Custom Fields.
The Last Created Contact trigger starts a Zap when a contact is added. It sends the following: ID, Customer Id, First Name, Last Name, Email, Phone, Notes, and Created At.
The Last Updated Contact trigger starts a Zap when a contact record is updated. It sends the following: ID, Customer Id, First Name, Last Name, Email, Phone, Notes, Created At, and Updated At.
The Last 48hrs Updated Contacts trigger checks on a schedule for any contact updated in the last 48 hours. It does not fire the moment a contact changes. It sends the same fields as Last Updated Contact.This trigger has one setup field, Page. This is where you need to enter a page number:
1: to get the first page of results
2: to get the second page of results
3: and so on
For most use cases, enter 1 to retrieve the first page of updated contacts from the last 48 hours. That’s typically all you need unless you’re dealing with a very large number of contacts.
The Get Customer Pipeline Statuses trigger finds customers in the pipeline status you choose. The statuses in the list come from your own FieldPulse account, so you can pick any status you have set up.Common statuses include New, Contact Attempted, Contact Made, Scheduled, Estimate Sent, Won, and Lost. Your list may also include custom statuses your team created.The trigger sends: Pipeline Status ID, Pipeline Status, Pipeline Status Type, and the customer’s ID, Name, Email, and Phone.
The Get Job Workflow Statuses trigger finds jobs by workflow and status. First choose a Workflow, then choose a Status that belongs to that workflow. Both lists show the workflows and statuses set up in your own FieldPulse account, so you can choose any of them.For example, if your account has a workflow with the statuses New, In Progress, and Completed, you can start a Zap when a job reaches Completed.The trigger sends: Workflow ID and Name, Status ID and Name, and the Job’s ID, Job Name, Start Time, End Time, Location ID and Address, Customer ID, Customer Name, Email, Phone, and Assigned Users.
The search actions look up an existing record so a later step can use it. All three work the same way.
Action
Search by
Search Customer
Search Value
Search Job
Search by text, Job ID, Customer ID, Project ID, Project Name, Job Start Date, Job End Date
Search Projects
Search by text, Customer ID, Project ID, Project Name
Each search action has two behavior settings, and both default the same way:
If no record matches, the Zap stops.
If more than one record matches, the Zap uses the first result and reports success.
Search Customer has one extra option that creates a new FieldPulse customer when the search finds none. If you leave this on, the Zap can create duplicate customers without anyone noticing. Turn it on only if that is what you want.
In Zapier, create a new Zap and choose FieldPulse as the trigger app.
For Trigger event, select Get Job Workflow Statuses.
Under Workflow, select the workflow your jobs use. Under Status, select Completed.
Select Test trigger to pull a recent job.
Add an action. Choose Email by Zapier, then select Send Outbound Email.
For To, enter the office or billing email address. In Subject and Body, build the message from the trigger data, such as the Job Name, Customer Name, Location Address, and Assigned Users.
