Connect PandaDoc to Reepay

Both apps 42PandaDoc 22Reepay 20

• Trigger
  Document completed

  Polling trigger. Fires when a document reaches completed status. Dedup by document id.

• Trigger
  Document completed (instant)

  Instant trigger: fires when a PandaDoc document reaches the completed state. Self-registering — APIANT creates the PandaDoc webhook when you turn the automation on and removes it when you turn it off, so there is nothing to paste. Only document_state_changed events with status document.completed are passed through; each fires once with the document id, name, status, created/modified/completed timestamps and the full document object.

• Trigger
  Document updated

  Polling trigger. Fires when a document is created or changes status. Dedup by document id + date_modified.

• Action
  Change document status

  Manually changes a document's status (e.g. to mark paid or voided). Only certain transitions are allowed.

• Action
  Create contact

  Creates a new contact.

• Action
  Create document from template

  Creates a new document from a template, with recipients, tokens, fields, and pricing tables.

• Action
  Create document link

  Generates a shareable session link for a recipient to view/sign a document.

• Action
  Delete contact

  Deletes a contact by ID.

• Action
  Delete document

  Deletes a document by ID.

• Action
  Download document PDF

  Returns the document as a PDF file. Use watermark options as needed.

• Action
  Find document by name

  Finds a document by name and emits its ID. An error occurs if none or more than one is found.

• Action
  Get document details

  Retrieves detailed data for a single document by ID, including recipients, tokens, fields, and metadata.

• Action
  Get document entered data

  Emits arrays of field and token names and values for the specified document.

• Action
  Get document status

  Returns the current status of a document by ID.

• Action
  Get template details

  Retrieves details for a template by ID, including roles, fields, tokens, and pricing tables.

• Action
  List contacts

  Lists contacts in the workspace.

• Action
  List documents

  Lists documents, optionally filtered by status, template, folder, or search query.

• Action
  List folders

  Lists document folders.

• Action
  List members

  Lists workspace members (users).

• Action
  List templates

  Lists available document templates.

• Action
  Send document

  Moves a draft document to sent status, optionally emailing recipients with a subject and message. Set silent to suppress notifications.

• Action
  Update contact

  Updates an existing contact by ID.

• Action
  Add coupon

  Create a new coupon. POST /v1/coupon

• Action
  Add credit

  Create a credit note/credit for a customer. POST /v1/credit

• Action
  Add customer

  Create a new customer. POST /v1/customer

• Action
  Add invoice

  Create an invoice for a customer. POST /v1/customer/{handle}/invoice

• Action
  Add plan

  Create a new subscription plan. POST /v1/plan

• Action
  Add subscription

  Create a new subscription for a customer. POST /v1/subscription

• Action
  Cancel subscription

  Cancel a subscription by handle. POST /v1/subscription/{handle}/cancel

• Action
  Delete customer

  Delete a customer by handle. DELETE /v1/customer/{handle}

• Action
  Get charge

  Retrieve a charge by handle. GET /v1/charge/{handle}

• Action
  Get coupon

  Retrieve a coupon by handle. GET /v1/coupon/{handle}

• Action
  Get customer

  Retrieve a customer by handle. GET /v1/customer/{handle}

• Action
  Get invoice

  Retrieve an invoice by id. GET /v1/invoice/{id}

• Action
  Get plan

  Retrieve the current version of a plan by handle. GET /v1/plan/{handle}/current

• Action
  Get subscription

  Retrieve a subscription by handle. GET /v1/subscription/{handle}

• Action
  List customers

  List all customers. GET /v1/list/customer

• Action
  List invoices

  List all invoices. GET /v1/list/invoice

• Action
  List plans

  List all plans. GET /v1/list/plan

• Action
  List subscriptions

  List all subscriptions. GET /v1/list/subscription

• Action
  Update customer

  Update an existing customer by handle. PUT /v1/customer/{handle}

• Action
  Update subscription

  Change/update an existing subscription by handle. PUT /v1/subscription/{handle}

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.