Connect Pipefile and Zipzign

Both apps 19Pipefile 11Zipzign 8

• Trigger
  File Request Created

  Triggers when a file request is created.

• Action
  Add File Request From Template

  Create a new file request from an existing template for one recipient (name/email/phone), optionally on behalf of a team member via X-Pipefile-On-Behalf-Of.

• Action
  Create Contact

  Add to contacts

• Action
  Delete Contact

  Delete a contact by id. Returns 204 No Content on success.

• Action
  Get Contact

  Retrieve one contact by id.

• Action
  Get File Request

  Retrieve detailed information about one file request by id, including contents, items, files, and tracking events.

• Action
  List Contacts

  Retrieve a paginated list of contacts, filterable by name/email/phone partial match.

• Action
  List File Request Templates

  Retrieve the list of file request templates available for creating new file requests, with optional name search.

• Action
  Search File Requests

  Finds all file requests matching this search query (contact name, email, tags, etc).

• Action
  Send Request

  Create and send a new request

• Action
  Update Contact

  Update name/email/phone of an existing contact by id.

• Trigger
  Document signed

  Fires when every signer on a ZipZign signable document has signed (the document.signed webhook event). Other ZipZign events delivered to the same endpoint are ignored.

• Trigger
  New document created

  Fires when a document is created; delivered via the document.created webhook event.

• Action
  Add document

  Create a new document (readable, signable, or payable)

• Action
  Delete document

  Marks a ZipZign document as deleted. Recipients then see a "no longer available" page. Documents that have been paid or signed cannot be deleted.

• Action
  Get document

  Fetches a document by ID, including its status, PDF link, signers, payment details and metadata. An error occurs if the document is not found.

• Action
  Submit signature

  Submits a signer's signature for a signable document using the signer's token from their signing link.

• Action
  Update document

  Replaces a document's content (HTML, template or PDF) and resets it to its active status, or renames it when only a name is given.

• Action
  Verify integrity

  Checks whether a signed document has been tampered with by comparing its current SHA-256 hash to the one recorded at signing time.

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