Connect FormHug and PandaDoc

Both apps 34FormHug 12PandaDoc 22

• Trigger
  New Or Updated Submission

  Triggers when a submission is created or edited on the chosen form.

• Action
  Add entry

  Creates a new entry (submission) on one of your FormHug forms.

• Action
  Add folder

  Creates a new folder for organizing forms, at the root or inside an existing folder.

• Action
  Add form

  Creates a new FormHug form, optionally with initial questions, locale, timezone, folder and header theme.

• Action
  Get current user

  Returns the FormHug user associated with the connected account, including their billing account and current subscription plan.

• Action
  Get entry

  Returns one submitted entry of a form, including every answer keyed by the form field's API code.

• Action
  Get form

  Returns a form's details, including its name, settings, folder and the full list of its fields.

• Action
  List entries

  Returns the entries (submissions) of one of your forms, optionally filtered and sorted.

• Action
  List folders

  Returns all folders owned by the connected FormHug user, newest first.

• Action
  List forms

  Returns the forms you created or that were shared with you, optionally filtered by name or folder.

• Action
  Update entry

  Updates an existing entry on a form. Only the fields you supply change; all other answers stay as they are.

• Action
  Update form

  Updates a form's name, description, locale, timezone, layout or question list. Only the values you provide are changed.

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