Connect CryptAPI and PandaDoc

Both apps 30CryptAPI 8PandaDoc 22

• Trigger
  Payment received (instant)

  Fires when a payment address created via Create payment address receives funds; CryptAPI calls the callback URL supplied at creation time with the payment details.

• Action
  Convert price

  Convert a value between a fiat currency and a cryptocurrency, or between two cryptocurrencies, for a given ticker.

• Action
  Create payment address

  Generate a new cryptocurrency payment address for a given ticker (e.g. btc, eth, trc20/usdt) that a customer can send funds to, with a callback URL for payment notifications.

• Action
  Estimate blockchain fees

  Estimate the blockchain network fee to forward a transaction to a wallet address, for a given cryptocurrency ticker.

• Action
  Generate payment QR code

  Generate a base64-encoded QR code image for a payment address, for a given cryptocurrency ticker.

• Action
  Get payment address logs

  Get the callback/payment activity log for a previously created payment address, for a given ticker.

• Action
  Get ticker info

  Get details (minimum transaction amount, fees, current price) for a specific cryptocurrency ticker.

• Action
  List supported cryptocurrencies

  List all cryptocurrencies and blockchains supported by CryptAPI, with logos, minimum transaction amounts, and fee tiers.

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

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