Connect PandaDoc to MoEngage

Both apps 30PandaDoc 22MoEngage 8

• 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 or Remove User From Cohort (Audience)

  Adds users to, or removes users from, a partner-synced custom segment (cohort) in MoEngage. Only users who already exist in MoEngage are matched; no new users are created.

• Action
  Create or update device

  Creates a new device for an existing MoEngage user, or updates the properties of one of that user's devices. MoEngage accepts the request and processes it shortly afterwards.

• Action
  Create or Update User

  Creates a new MoEngage user or updates the attributes of an existing user.

• Action
  Delete users

  Requests permanent deletion of one MoEngage user, identified by customer ID or MoEngage ID. The user stays active for a 24-hour buffer period and cannot be retrieved once deleted.

• Action
  Fetch Campaign Report

  Downloads a generated MoEngage campaign report file by its file name. Reports can be downloaded for 7 days after they are generated.

• Action
  Find users

  Returns the MoEngage user profiles that match the Customer IDs or MoEngage IDs you specify, and lists any IDs that were not found.

• Action
  Import User Event

  Records one or more events a user performed, with their attributes and times, on the user's MoEngage profile. Creates the user if needed.

• Action
  Merge users

  Merges duplicate MoEngage user profiles by moving each merged user's data into the retained user. MoEngage cannot undo a merge, so check the user IDs before running it.

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