Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

PandaDoc

PandaDoc integration for Flows360 workflows.

CategoryContent And Files
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect PandaDoc with Flows360

PandaDoc integration for Flows360 workflows.

Use the PandaDoc connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 8 actions and 3 triggers.

Available actions

  • Create Document from Template
  • Create Attachment
  • Create or Update Contact
  • Find Document(s)
  • Get Document Attachment
  • Get Document
  • Download Document
  • Custom API Call

Available triggers

  • Document Completed
  • Document State Changed
  • Document Updated

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: PandaDoc
  • Package: @activepieces/piece-pandadoc@0.2.0
  • Exact artifact digest: sha256:4c8b498cdcbdf4288079b9f6eeeb017522e0a4b91fdaa246f80d4a1aff23212b
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Document from Template (createDocumentFromTemplate), Creates a document from a PandaDoc Template. Classification: read.
  • Create Attachment (createAttachment), Adds an attachment to a document. Classification: read.
  • Create or Update Contact (createOrUpdateContact), Creates a new or update an existing contact. Classification: read.
  • Find Document(s) (findDocument), Finds documents based various filter. Classification: read.
  • Get Document Attachment (getDocumentAttachments), Retrieves details of a specific attachment from a document. Classification: read.
  • Get Document (getDocumentDetails), Retrieves comprehensive document data. Classification: read.
  • Download Document (downloadDocument), Downloads a document as PDF. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Document Completed, webhook.
  • Document State Changed, webhook.
  • Document Updated, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects11
Supported actionsNot published
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Document from Template Yes No Creates a document from a PandaDoc Template.
Create Attachment Yes No Adds an attachment to a document.
Create or Update Contact Yes No Creates a new or update an existing contact.
Find Document(s) Yes No Finds documents based various filter.
Get Document Attachment Yes No Retrieves details of a specific attachment from a document.
Get Document Yes No Retrieves comprehensive document data.
Download Document Yes No Downloads a document as PDF.
Custom API Call Yes No Make a custom API call to a specific endpoint
Document Completed Yes No webhook trigger declared by the pinned package.
Document State Changed Yes No webhook trigger declared by the pinned package.
Document Updated Yes No webhook trigger declared by the pinned package.

Triggers

Document Completed · Webhook

Triggers when a document is completed.

Inputs

  • template_filter · array
  • folder_filter · array
Document State Changed · Webhook

Triggers when a document status changes.

Inputs

  • filter_status · array
Document Updated · Webhook

Triggers when a document is updated.

Inputs

  • template_filter · array
  • folder_filter · array
  • update_type_filter · array

Setup

Setup

  1. Add the PandaDoc connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-pandadoc@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 8 actions and 3 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required PandaDoc connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-pandadoc@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com