📖 Table of Contents

Use the Yousign integration events to trigger HubSpot workflows

Step-by-Step: Create a Workflow with Yousign Events

Boost your productivity by using Yousign signature request events as triggers in HubSpot workflows. Automations let you keep your CRM perfectly up to date and help your team take timely action based on the progress of signature requests — all without manual intervention.

Workflows are only available in certain paid HubSpot plans (Professional and Enterprise).

Use the Yousign integration events to trigger HubSpot workflows

Connecting Yousign events to HubSpot workflows unlocks new automation capabilities. Here are the main benefits:

Automate deal progression: Move a deal forward when a document is signed.
Improve responsiveness: Notify your team when a signer opens a document or declines to sign.
Keep CRM data clean: Update properties like signature status automatically.
Trigger follow-ups: Launch marketing or sales sequences based on document progress.

Step-by-Step: Create a Workflow with Yousign Events

Here’s how to create a workflow that reacts to Yousign events in HubSpot:

1. Go to “Workflows” in HubSpot

Navigate to: Automation → Workflows → Click Create workflow

Choose the object the workflow should be based on:

Most often, this will be Deals, Companies, or Contacts, depending on where you create your signature requests from.

2. Set the Enrollment Trigger

Select: Activity → Integration Events → Yousign

You will see an event named Yousign Signature Request.

This event captures all types of signature request activity, including:

Request status changes (e.g. Done, Canceled, Expired, etc.)
Signer opened the signature link
Signer signed the request

3. Target only specific events (optional)

Signature request status: You can then filter on one or multiple signature request statuses, such as : Done, Canceled, Expired…

See full list of request statuses

Status	Meaning
`Draft`	The signature request has been initiated but has not yet been sent to signers. You can edit the signature request at any time before sending.
`Approval`	The signature request is awaiting validation from the defined approver(s).
`Ongoing`	The signature request has been sent to signers. Not all signatures have been completed yet.
`Done`	All signers have signed the documents in the signature request.
`Rejected`	The signature request was rejected by one of the approvers.
`Decline`	The signature request was declined by one of the signers.
`Canceled`	The signature request was sent and then cancelled by a user.
`Expired`	One or more approvers and/or signers did not approve and/or sign your documents before the expiration date of your signature request. However, you can reactivate your expired signature request to extend its signing deadline.
`Deleted`	The signature has been put in trash.

Event name: You can then filter on one or multiple event names, amont the following :
- Signature request status has changed
- Signer has opened the signature link
- Signer has signed

4. Add Workflow Actions

Once the trigger and filters are configured, choose what happens next.

Workflow Examples (“Recipes”)

Here are some ready-to-use workflow “recipes”:

1. Move a Deal to “Closed Won” When Signature is Completed

Trigger: Signature Request Status = Done
Action: Update deal stage to Closed Won

See example

2. Notify Sales Rep When a Document is Opened

Trigger: Event name = Signer has opened the signature link
Action: Send internal notification to the deal owner

Useful to remind sales to follow up after a document was viewed but not signed.

See example

3. Alert Legal When a Request is Declined or Rejected

Trigger: Signature Request Status = Declined or Rejected
Action: Create a task or send Slack/Email to legal team

4. Update a Custom Property with Signature Status

Trigger: Event name = Signature request status has changed
Action: Update custom property (e.g. Last Yousign Status) on the deal or contact

This keeps your CRM data up to date and allows better reporting.

Best Practices

Use branching logic to handle different statuses differently within the same workflow.
Test with internal signature requests before rolling out to production.
Name your workflows clearly, e.g., [Yousign] Auto Move Deal on Signature Done.