Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI TesterBlog

Send Document to PDF4me-Workflow in Zapier

Send Document to PDF4me-Workflow is a Zapier action by PDF4me that hands a file off to a pre-built, multi-step PDF4me Workflow instead of a single PDF4me action. Trigger it when a document needs a sequence of operations, such as extraction, splitting, and conditional routing, that a single Zapier step cannot express. The action returns a job ID and status for tracking, not the processed file itself.

What this action does

PDF4me Send Document to PDF4me-Workflow uploads a file from your Zap and starts a specific, already-configured PDF4me Workflow, such as a multi-step invoice pipeline, contract assembly sequence, or document quality-control process. The processing logic itself lives in the PDF4me Workflow dashboard, not in the Zap, so this action stays a single simple step no matter how complex the underlying workflow is.

Related Blog Posts
No blog post yet for this feature — coming soon.
In the meantime, browse the PDF4me blog for tutorials and workflows across every platform.
Visit the blog →

Authenticating Your API Request​

To access the PDF4me Web API through Zapier, every request must include proper authentication credentials. Authentication ensures secure communication and validates your identity as an authorized user.

Get your API Key

Important Facts You Should Not Miss​

The file is not returned directly to Zapier
The document is processed inside the PDF4me Workflow. Retrieve results through workflow completion notifications or a separate PDF4me action.
The workflow itself is built outside Zapier
Create and manage the multi-step logic in the PDF4me Workflow dashboard. This action only selects and triggers an existing workflow.
Status reflects real-time execution state
Queued, Processing, Completed, or Failed. Use it to route follow-up steps or wait for completion.
PDF4me Send Document to PDF4me-Workflow Zapier configuration - File field required, Select PDF4me-Workflow dropdown
Set up action: map File and choose the target PDF4me Workflow from the dropdown.

Parameters​

Complete list of parameters for the Send Document to PDF4me-Workflow action.

Required in the Zapier UI: both File and PDF4me Workflow are required.

ParameterRequiredWhat it doesExample
FileRequiredFile to be uploaded and processed by the PDF4me Workflow, mapped from a previous step using full file content, not a reference.[Document File]
PDF4me WorkflowRequiredSelects the target workflow from your list of active PDF4me Workflows. Manage and view workflows in the PDF4me Workflow dashboard.Invoice Processing Workflow
Map File using full file content

Use the + button next to File to map from an earlier Zap step. Select the option that provides full file content, not "Exists but not shown" references.

Output​

The PDF4me Send Document to PDF4me-Workflow action returns job tracking data for monitoring workflow execution. The file itself is not returned to Zapier.

FieldTypeWhat it contains
JobIdStringUnique ID of the created workflow job, used for tracking execution.
StatusStringCurrent status of workflow execution: Queued, Processing, Completed, or Failed.

How Do I Trigger a PDF4me Workflow from Zapier?​

  1. Add PDF4me to your Zap and choose Send Document to PDF4me-Workflow under Workflow.
  2. Connect your PDF4me account, or select an existing connection.
  3. Map File from a previous step, using full file content rather than a reference.
  4. Select the target PDF4me Workflow from your list of active workflows.
  5. Test the step, then use the returned JobId and Status to track or route based on execution progress.

What Happens After the Workflow Is Triggered?​

The action itself only starts the workflow and returns a JobId and Status. The actual multi-step processing, such as extraction, splitting, watermarking, or conditional routing, runs inside the PDF4me Workflow engine, separate from the Zap. To get the processed result back, check the workflow's completion notification or call a separate PDF4me action once the workflow finishes.

Typical Setups​

Workflow ExamplesCommon Zapier + PDF4me Workflow patterns using Send Document to PDF4me-Workflow.
Invoice email to multi-step processing
  1. A Gmail trigger fires when a vendor invoice email arrives with a PDF attachment.
  2. PDF4me Send Document to PDF4me-Workflow uploads the attachment and selects the invoice-processing PDF4me Workflow.
  3. The PDF4me Workflow itself performs OCR, data extraction, and conditional routing based on amount thresholds.
  4. A downstream Zap step imports the extracted data once the workflow's completion notification arrives.
Document upload to quality-control pipeline
  1. A document-management trigger fires when a new file is uploaded.
  2. PDF4me Send Document to PDF4me-Workflow sends it to a quality-control PDF4me Workflow that validates format, corrects orientation, and applies watermarks.
  3. The Zap polls or receives a notification on the returned JobId to know when the quality check is complete.
Contract data to assembly workflow
  1. A contract-approval trigger fires once internal sign-off is complete.
  2. PDF4me Send Document to PDF4me-Workflow triggers a contract-assembly PDF4me Workflow that merges exhibits and applies protection.
  3. The assembled contract is routed for signature once the PDF4me Workflow reports Completed.

Practical Tips​

The processed file does not come back to this action
Design your Zap to retrieve results via a PDF4me Workflow completion notification or a follow-up action, not from this step's output.
Build the workflow first
Create and test the PDF4me Workflow in its dashboard before wiring this Zapier action to it. The action can only select an already-existing workflow.
"Exists but not shown" breaks the File field
Map File using the option that provides full file content instead of a reference.
Poll or route on Status
Use the returned Status (Queued, Processing, Completed, Failed) to branch your Zap logic rather than assuming immediate completion.
One file per run
Each execution triggers the workflow with one file. Loop this action if you need to process a batch of files.

Cheat Sheet​

FieldValue
ActionSend Document to PDF4me-Workflow
File[Document File]
PDF4me WorkflowInvoice Processing Workflow
Output to map forwardJobId, Status
Where to build the workflowPDF4me Workflow dashboard (dev.pdf4me.com/pdf4me-workflows)

Frequently Asked Questions​

Does this action return the processed document back to Zapier?+
No. The file is processed inside the PDF4me Workflow, not returned directly to Zapier. Retrieve results through PDF4me Workflow completion notifications or a separate PDF4me action.
Where do I create or manage the PDF4me Workflow itself?+
PDF4me Workflows are built and managed in the PDF4me Workflow dashboard, separately from Zapier. This action only triggers an existing, already-configured workflow.
What does the Status field mean?+
Status reflects the workflow execution state: Queued, Processing, Completed, or Failed. Poll or route on this value to know when the workflow has finished.
Why does my File field show "Exists but not shown"?+
That label means the mapped field is a reference, not the actual file content. Remap File using the option that provides full file content instead. See Zapier's help center for general tips on mapping file fields between steps.
Can this action run more than one workflow at a time?+
Each run of this action triggers one PDF4me Workflow with one file. To process multiple files, run the action once per file, such as inside a loop.

Same Task on Other Platforms​

Industry Use Cases & Applications​

  • Invoice Processing: Trigger multi-step invoice workflows
  • Financial Reporting: Process complex financial document workflows
  • Compliance Documents: Automate regulatory document processing
  • Batch Processing: Handle month-end document batches

Get Help​

Zapier IntegrationGet your API KeyZapier Documentation