Connect PandaDoc to Neon Postgres

Both apps 51PandaDoc 22Neon Postgres 29

• 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 branch

  Create a new branch in a Neon project.

• Action
  Add compute endpoint

  Creates a compute endpoint (a Neon compute instance) on a branch of a Neon project. A branch can have one read-write endpoint and multiple read-only endpoints.

• Action
  Add database

  Creates a new Postgres database in a Neon project branch, owned by an existing role.

• Action
  Add project

  Creates a new Neon Postgres project with its default branch, database, role and compute, and returns the project along with its connection details.

• Action
  Add role

  Creates a Postgres role in the specified Neon project branch. Connections to the branch's active compute are dropped while the change applies.

• Action
  Delete branch

  Delete a branch by project_id and branch_id.

• Action
  Delete compute endpoint

  Deletes a compute endpoint from a Neon project. Existing connections to the compute are dropped. If the compute does not exist or was already deleted, the step still succeeds with an empty result.

• Action
  Delete database

  Deletes the specified database from a branch of a Neon project.

• Action
  Delete project

  Deletes a Neon project and all its branches, compute endpoints, databases and roles. The project can be recovered within 7 days.

• Action
  Delete role

  Deletes the specified Postgres role from a Neon branch.

• Action
  Get branch

  Retrieves details of a branch in a Neon project.

• Action
  Get compute endpoint

  Retrieve details about a compute endpoint.

• Action
  Get connection URI

  Retrieve a Postgres connection URI for a database/role/branch/endpoint combination.

• Action
  Get database

  Retrieves details of a database on a Neon project branch.

• Action
  Get project

  Retrieves the details of a Neon project, including its settings, compute configuration, history retention, owner and current usage metrics.

• Action
  Get role

  Retrieves details about a Postgres role (user) on a Neon branch.

• Action
  Get role password

  Retrieves the password for a Postgres role on a Neon branch.

• Action
  List branches

  Retrieve a list of branches for a Neon project.

• Action
  List compute endpoints

  Lists the compute endpoints (Neon compute instances) in a project.

• Action
  List databases

  Lists the databases on a branch of a Neon project.

• Action
  List operations

  Lists the operations (asynchronous actions such as starting a compute or creating a branch) Neon performed on a project. Operations older than 6 months may no longer be available.

• Action
  List projects

  Lists the Neon projects accessible to the connected account, optionally filtered by name/ID or organization.

• Action
  List roles

  Lists the Postgres roles on a Neon project branch.

• Action
  Start compute endpoint

  Start (resume) a suspended compute endpoint.

• Action
  Suspend compute endpoint

  Suspends the specified Neon compute endpoint (scales it to zero).

• Action
  Update branch

  Update a branch's properties (e.g. name, protected) by project_id and branch_id.

• Action
  Update compute endpoint

  Updates an existing compute endpoint in a Neon project by ID.

• Action
  Update database

  Updates the name or owner of a database on a Neon project branch.

• Action
  Update project

  Update settings for a Neon project by project_id.

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