How to Identify Zapier-Triggered Documents in BoldSign Audit Trail

In BoldSign, the Audit Trail provides a complete record of all document activities, ensuring transparency and accountability. When documents are sent through Zapier integrations, it is important to distinguish these automated requests from those initiated manually by users.

To make this distinction clear, we recommend adding a prefix to the document title (for example, [Zapier Integration] Sales Contract). This prefix allows anyone reviewing the Audit Trail to easily identify that the document was dispatched via Zapier, helping maintain clarity in integration-driven workflows.

Information captured in the Audit Trail

BoldSign Audit Trail records the following details for each document:

• Document Information: Includes the prefixed title (e.g., [Zapier Integration] Sales Contract), document ID, type, status, signing order, page count, and timestamps for when the document was sent and completed.

• Sender and Recipient Information: Captures names, email addresses, IP addresses, and devices used by all participants involved in the document workflow.

• Integration Activity: Logs all actions performed via Zapier, including:

  • The exact timestamp of the action

  • The IP address and device used by the integration service

• Signature Information: Specifies the type of signature applied (e.g., typed, drawn, uploaded) and confirms acceptance of electronic signature disclosures.

• Timestamps: Provides precise logs of all actions, including sending, viewing, signing, and document completion.

• User Activity Log: Tracks user interactions such as viewing, signing, or reassigning the document, along with corresponding timestamps.

Prefixing document titles

By prefixing document titles (e.g., [Zapier Integration] Sales Contract), organizations can clearly track the point of origin for signature requests. This ensures reviewers can quickly distinguish between manual actions and automated integration-driven workflows in the Audit Trail.

Example scenario

• A new Sales Contract record is created in Salesforce.

• Zapier uses the BoldSign API to automatically send a document based on a predefined template.

• Dynamic fields such as client name and contract amount are filled using data from the trigger app.

• The document title is prefixed with [Zapier Integration], making it clear in the Audit Trail that the request originated from an integration.

In the above screenshot, a document is generated using a predefined template. The title marked as [Zapier Integration] Sales Contract clearly shows that the document was dispatched through Zapier automation, ensuring full visibility and accuracy in the audit trail.

Below is a sample of the Zapier Integration audit trail document:

In the above screenshot, the document is shown with the [Zapier Integration] prefix in its title. This indicates that the request was automatically triggered by a Zapier workflow rather than sent manually. The Audit Trail captures the exact timestamp of the Zapier action along with integration details, making it clear that the document originated from an automated process.

Notes

Adding a prefix to document titles is not limited to Zapier workflows. Zapier triggers BoldSign to automatically send the document based on a predefined template. This ensures the Audit Trail clearly reflects the origin of each signature request, whether triggered by an integration or initiated directly by a user.