Zapier and Make
Run PDF tools and react to finished runs from Zapier and Make with an API key.
What the apps do
The PDF Loft apps for Zapier and Make are built on the public API and webhooks, so anything they do you can also do with an API key. They are included in the Team plan and above, and every run draws from the shared task pool.
| Kind | Name | What it does |
|---|---|---|
| Trigger | Run finished | Starts when a run succeeds or fails. Uses a webhook, so it fires at once instead of polling. |
| Trigger | Document saved | Starts when a document is saved to the library. |
| Action | Run a PDF tool | Uploads a file, runs a tool with its options and returns the finished run. |
| Action | Save a document | Uploads a PDF and saves it to the library. |
| Search | Find a run | Fetches a run by its id. |
Connect an account
- In PDF Loft, open Settings, then Developers, and make an API key with the scopes
tools:run,jobs:read,documents:read,documents:writeandwebhooks:manage. - In Zapier or Make, add the PDF Loft app and paste the key when it asks to connect.
- The app checks the key by listing tools. A revoked key fails on its next call.
How triggers work
A trigger registers a webhook endpoint when you turn a Zap or scenario on, and deletes it when you turn it off, through POST /v1/webhooks and DELETE /v1/webhooks/{id}. Deliveries are signed, retried and listed in the delivery log like any other webhook. See Webhooks.
The apps are built but not yet published to the Zapier or Make directories, so they cannot be added from those directories today. Until they are, use the HTTP and webhook modules of either service with an API key and the routes in the reference.