Auto-send contracts when a HubSpot deal hits Contract Sent

By General Input

When a deal moves to Contract Sent in HubSpot, fire off the right Dropbox Sign template to the primary contact and ping the deal team in Slack.

Integrations

  • HubSpot
  • Dropbox Sign
  • Slack Bot

Type

Agentic Task

Categories

  • Sales
  • Operations

Build me an agent workflow that handles contract sending whenever a deal advances in HubSpot.

Trigger: a HubSpot deal property change webhook. The agent should only act when the deal's stage just changed to our Contract Sent stage. Treat the exact stage name as a configurable variable so I can rename it later.

When the trigger fires, do this:

1. Pull the full deal from HubSpot with its associated primary contact and company using Get Deal with associations. I want at minimum the deal name, amount, deal type, region, owner, plus the primary contact's first name, last name, and email, plus the company name.

2. List my Dropbox Sign templates with List Templates and pick the one that fits the deal. Match on deal type first, then region, then amount tier. Write the matching rules in plain English in the workflow so an AE can tweak them later without code. The agent should reason over deal properties to choose the template, not use a hard-coded mapping.

3. Send the contract with Send Signature Request with Template, pre-filling the signer name and email from the primary contact and using the deal name in the request title and subject so it is easy to find later.

4. Create a Note on the HubSpot deal (Create Note, associated to the deal) recording the Dropbox Sign signature request ID, the template that was used, and the date sent.

5. Post a short message to our deal team's Slack channel via Send a Message. Include the contact name, deal amount, template used, and a link back to the HubSpot deal record. Write the copy in plain English so the AE knows the contract went out and what was sent.

Important guardrails: if no template clearly fits the deal, skip the send, post a Slack message explaining why so the AE can step in, and still log a note on the deal so I can follow up. If a signature request has already been sent for this deal (check for an existing signature note before sending), do not re-send. The Slack channel ID and the stage name should both be configurable variables.

Related prompts

Explore more prompts
A brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasoniMessage campaign console with pre-flight checks and delivery boardLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsA searchable RFP answer library your bid team drafts fromLinkedIn Ads budget pacing dashboard for every client account