- Home
- Resources
- Integrations
- PepaDocs
PepaDocs Zapier integrationAutomate PepaDocs with Zapier.
The PepaDocs Zapier integration gives you 6 triggers, 5 actions and 0 searches. Every trigger is instant: a new report, a changed database line or a newsletter sign-up starts your Zap at once, and five actions create, edit, sort, share or delete reports.
Verified Trustpilot reviews · AI, automation & growth agency
What the PepaDocs Zapier integration does
It links your PepaDocs account to Zapier, so the reports your technicians fill in on site, the lines of your PepaDocs databases and your newsletter sign-ups can start automations, and so other tools can create, edit, sort, share or delete reports in PepaDocs.
Three results teams build with it. A report sent to the client the moment it exists: Document: New Report starts the Zap, Create Report PDF Link makes a link, and your email tool sends it. Reports opened from the job list: a ticket in your helpdesk runs Create a Report, so the technician finds a blank report on the right model. A database kept in sync: the three DataBase triggers copy each new, edited or deleted line to a spreadsheet the office reads.
What Zapier does not do here matters too. There is no search step, so a Zap cannot look up a report by client or date: Edit a Report, Delete a Report and Create Report PDF Link all need the report's ID handed over by an earlier step. Categorize a Report only accepts a category that already exists in your model; it will not create one. And the newsletter triggers only listen: no action adds or removes a subscriber.
If you are comparing tools before you build, see n8n vs Zapier. For a guided start on the editor, there is the Zapier training.
Zapier words in plain English
Seven terms, one line each. You will see them on every screen of the editor.
- Zap
- The automation you build: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in PepaDocs that starts the Zap, such as a new report. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you, like making a PDF link.
- Task
- The unit Zapier bills: one action that completes successfully. Your plan's allowance is a count of those.
- Instant trigger
- A trigger the app reports itself, the moment the event happens, so nothing waits for a timed check by Zapier.
- Filter
- A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your PepaDocs account linked to Zapier once, then reused by every PepaDocs step of every Zap.
What a PepaDocs Zap really costs
The trigger never costs a task. Each action that succeeds costs one, and an action that fails is not counted against your plan.
- Trigger fires0 tasks
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, works on Free
PepaDocs is not a premium app, so it runs on the free plan: 100 tasks a month, unlimited Zaps, two steps per Zap. Document: New Report plus Create Report PDF Link fits. Sending that link by email is a second action, so the Zap turns multi-step and needs a paid plan, as does any filter. Each action counts on its own: three actions, three tasks per report. The polling grid does not apply, all 6 triggers being instant.
Connect PepaDocs to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a PepaDocs account, with access to the report models, tables and newsletters the Zap will use.
- 02
Pick PepaDocs
Type PepaDocs in the search box of the dialog, select it, then click Add connection. A new tab opens on the PepaDocs side to finish linking the accounts.
- 03
Sign in and allow access
Log in to PepaDocs in that tab and grant Zapier access to the account. The connection is saved once, and every PepaDocs step of every Zap you build reuses it.
Your first Zap: email each new report as a PDF link
GoalWhen a technician creates a report in PepaDocs, make a PDF link for it and send that link to the client by email.
- 01
Pick the trigger
Build: choose PepaDocs and Document: New Report, select your connection, then pick the report model to watch. That choice is required.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent reports of that model, so you map the next steps on a real report, not a blank.
- 03
Add Create Report PDF Link
Add PepaDocs again with Create Report PDF Link and map the Report Id from the trigger. The step returns a unique link with its own access code.
- 04
Add the email step
Pick your email tool and its send action, then place the PDF link from the previous step in the message meant for the client.
- 05
Test and publish
Test each step and read what came back, then click Publish. With two actions this is a multi-step Zap, so it runs on a paid plan.
PepaDocs triggers: 6 instant events
6 events start a Zap when something happens in PepaDocs, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.
Document: New Report
Instant triggerIn Zapier“Triggers when a new report is created.”
A report created in PepaDocs on the model you chose starts the Zap, with that report ready for the next step.
DataBase: When a Line Is Deleted
Instant triggerIn Zapier“Triggers when a line of data is deleted in a choosed FlexData of your entity.”
Removing a line from one of your PepaDocs databases (FlexData tables) sets this Zap off, so a deletion never goes unseen elsewhere.
DataBase: When a Line Is Edited
Instant triggerIn Zapier“Triggers when a line of data is edited in a choosed FlexData of your entity.”
This one waits for changes to a line that already exists in the table you pick, rather than new lines.
DataBase: When a New Line Is Created
Instant triggerIn Zapier“Triggers when a new line of data is created in a choosed FlexData of your entity.”
A fresh line added to a chosen PepaDocs table starts the Zap, the natural way to spread new reference data.
Newsletter: When Someone Delete a Registration
Instant triggerIn Zapier“Triggers when someone remove himself from the registration.”
Someone taking themselves off a PepaDocs newsletter is the signal here; the Zap gets that unsubscribe.
Newsletter: New Registration Confirmed From Someone
Instant triggerIn Zapier“Triggers when someone validate and confirm a new registration of his/her email into the system.”
Only confirmed sign-ups count: the Zap starts once the person has validated their registration, not at the first form entry.
PepaDocs actions: create, edit, sort, share, delete
PepaDocs gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Categorize a Report
ActionIn Zapier“Categorize a given report according to one of the categories you have”
Files a report under one of your categories, so the team finds it where it should be.
Create a Report
ActionIn Zapier“Creates a report based on one of your pepadocs models.”
Opens a new report in PepaDocs on the model you select, ready for a technician to complete.
Create Report PDF Link
ActionIn Zapier“Creates a PDF URL to access the report, the url is unique and contains an access code, which means that sharing the url allow anyone to access the report”
Produces a unique PDF link to a report, with an access code built into it, ready to send.
Delete a Report
ActionIn Zapier“Delete the selected report”
Removes the selected report from PepaDocs, using the report ID handed over by an earlier step.
Edit a Report
ActionIn Zapier“Edit some fields of a report”
Changes some fields of a report that already exists, picked by its model and its ID.
When a PepaDocs Zap breaks
Zapier attaches no help article to PepaDocs, and no rate limit of its own is documented. What breaks is what breaks on any Zap, plus a few traps that come from the operations themselves.
Four cases worth knowing before you switch it on. For the rest, see Zapier troubleshooting.
The report Zap that loops
Document: New Report followed by Create a Report on the same model is a loop: each new report starts the Zap again and the task count drains fast.Old reports are not replayed
A Zap reacts only to what happens after it is published. Reports written last week stay where they are; moving that backlog is a separate job.A table import gets held back
Loading many lines into a FlexData table at once sends a huge batch to the trigger, and Zapier's flood protection can hold it back.The category does not exist
Categorize a Report only accepts a category already defined in your PepaDocs model. A misspelt or new name will not do: add the category to the model first.
Need help automating PepaDocs with Zapier?
A person reads every message.



