What does the Zapier integration do?

Powered Now and Zapier

What does the Zapier integration do?

Give a tradesperson a yard full of materials and the right tools, and what could they build? Quite a lot. The answer depends on what they need and how they put everything together.

Our Zapier integration works in much the same way. It gives you the building blocks to connect Powered Now with other apps and automate repetitive admin. What you build depends on the task you want to get off your plate.

Zapier connects apps through automated workflows called Zaps. Each Zap has something that starts it, called a trigger, followed by one or more actions. For example, a custom Zap could take an enquiry from a compatible website form and create a customer in Powered Now, or copy information from Powered Now into a spreadsheet. The other app needs to support the relevant steps too.

Powered Now makes the connections described below available for custom Zaps. You will need to build and configure a Zap for the workflow you want to use. That might sound scary, but Zapier's Co-Pilot AI makes the whole process a hands-off breeze.

On top of that, we're building a number of Zapier templates based on the Zaps our customers request most often. We expect these to be available very soon, so make sure you are signed up to our email updates for the latest features.

What you can do with Powered Now?

These are the types of information a custom Zap can work with, and the tasks it can carry out in Powered Now.

Information	What your custom Zap can do
Customers	Look up customers, create new customer records and update existing customer details.
Customer sites	View, add and update additional sites belonging to a customer.
Documents	Look up existing documents and update their supported details.
Projects	Look up projects (or "Jobs", as some systems might call them), create new projects and update existing projects records.
Projects notes	Read notes, add notes to a project, and update existing notes. You can also look up notes across your company.
Appointments	Look up appointments, create appointments linked to a project and update existing appointments.
Payments	Look up payment records, create new payment records and update existing ones.
Files and file groups	Look up files and groups of files, download files, create groups, add files to new or existing groups and update supported file or group details. These can also be linked to a projects.
Notifications	Look up, create and update Powered Now notifications, including their read or unread status.
Types and statuses	Look up appointment types, payment types, contact method types, and customer, projects and appointment statuses so your Zap can use the correct options.
Subscription information	Read subscription information for your company.
Event notifications	Set up a connection that sends information when a supported event happens in Powered Now. You can stop these event notifications by removing the subscription.

For example, you could build a Zap to create a customer from a website enquiry, add a note to an existing projects, or use payment records in a reporting spreadsheet. Each workflow needs to be configured around the information and actions supported by both apps.

Available API requests

This section is for anyone building a custom Zap or working with someone who will set it up for them. An API lets software exchange information. An endpoint is the address used to access a particular type of information, and the request method tells Powered Now what you want to do with it.

Request methods

Method	What it does
GET	Retrieve information, such as a list of projects or a particular customer record.
POST	Submit information to perform an action, such as creating a customer, adding files to a group or registering a webhook subscription.
PUT	Update an existing record. Several Powered Now endpoints accept only the fields you want to change.
PATCH	Apply a partial update to an existing record where supported.
DELETE	Remove a webhook subscription. This is the only DELETE operation available through this integration.

In standard HTTP terminology, PUT replaces a resource and PATCH makes a partial change. Powered Now allows partial PUT updates for customers, documents, appointments and notifications. For appointments and notifications, PUT and PATCH explicitly provide the same partial-update behaviour. Follow the requirements of the endpoint you are using.

Supported methods by data type

Yes indicates that the method is available for that data type. A dash means it is not available. Read the notes below for operations that involve a specific route or an extra step.

Data type	GET	POST	PUT	PATCH	DELETE
Customers	Yes	Yes	Yes	-	-
Customer additional sites	Yes	Yes	Yes	-	-
Documents	Yes	-	Yes	-	-
File groups	Yes	Yes	Yes	Yes	-
Files	Yes	-	Yes	Yes	-
Projects	Yes	Yes	Yes	-	-
Project notes	Yes	Yes	Yes	Yes	-
Company notes	Yes	Yes	Yes	Yes	-
Payments	Yes	Yes	Yes	-	-
Appointments	Yes	Yes	Yes	Yes	-
Appointment types	Yes	-	-	-	-
Payment types	Yes	-	-	-	-
Notifications	Yes	Yes	Yes	Yes	-
Customer statuses	Yes	-	-	-	-
Project statuses	Yes	-	-	-	-
Appointment statuses	Yes	-	-	-	-
Contact method types	Yes	-	-	-	-
Subscription information	Yes	-	-	-	-
Webhook subscriptions	-	Yes	-	-	Yes

Details to account for when building your Zap

Reading information. Most GET-enabled data types provide both a list endpoint and an individual-record endpoint using an ID. Customer additional sites and contact method types provide list endpoints, while subscription information has a single retrieval endpoint. Filtering and pagination are available on selected list endpoints.

Customers and sites. Creating a customer requires main_site information containing contact and address details. The customer sites endpoints handle additional sites only, identified as type 4. Main, invoice and registered site information is accessed through the customer endpoint.

Documents. Documents support GET and PUT. Use these to retrieve documents and update the fields accepted by the document endpoint.

Notes. Both the job notes routes and the company notes routes support GET, POST, PUT and PATCH. A new note must belong to a job: the job-specific route takes jobId from the URL, while POST /structured/notes requires job_id in the request body.

Files and file groups. File groups and files have both company-level and job-specific routes. POST creates a group containing one or more files, or adds files through the group's /files route. It returns a presigned upload URL for each file. Upload the file content using the returned URL, then confirm the upload through the file endpoint using PUT or PATCH with status set to "uploaded". GET for an individual file returns its metadata and a presigned download URL. Updating a file means updating its metadata and/or confirming an upload.

Appointments and notifications. Creating an appointment requires action, dt_start, dt_end, appointmenttype_id and job_id. Use the appointment types lookup for the appropriate type ID. Creating a Powered Now notification requires action, with an optional job_id. Notification updates can include read, unread or sent status.

Reference information. GET lookups return the available appointment types, payment types and statuses. Contact method types are available through GET /data/global/ContactMethodType; their IDs are used in customer contact_methods[].type_id.

Webhooks. A webhook sends information to a receiving URL when a supported event occurs. POST /webhook/manage/subscribe/{eventType} registers that subscription. The response includes a Svix signing secret so the receiver can verify webhook signatures. DELETE /webhook/manage/unsubscribe/{eventType} removes the subscription for that event type.

Want to stay in the loop? Sign up for marketing emails below.