Quick overview
This workflow receives e-signature status webhooks,logs and updates contract records in Airtable,and when a contract is completed it uses Groq to generate an onboarding checklist that is sent via Gmail,created as a Trello card,and posted to Slack,while also running a daily Slack alert for stale deals.
How it works
- Receives an HTTP POST webhook from your e-signature tool whenever a contract status changes.
- Verifies a shared secret from the request and extracts key fields like document ID, status, client details, and contract amount.
- Updates the matching Airtable contract record with the latest status update, and if the status is completed it marks the contract as signed with a signed date.
- Sends the signed contract’s service details and amount to Groq to generate a structured engagement summary and 4–6 onboarding checklist items.
- If the contract amount meets your high-value threshold, posts a high-value alert to a dedicated Slack manager channel.
- Sends the AI-generated onboarding summary and checklist to the client via Gmail, creates a Trello card for the onboarding work, and posts a signed-contract notification to the sales Slack channel.
- Runs daily on a schedule to find Airtable contracts still in sent/viewed status past your cutoff date and posts a “deal going cold” reminder to Slack.
Setup
- Create an Airtable “Contracts” table with fields including document_id, client_name, client_email, status, contract_amount, service_details, last_status_update, and signed_date, and add an Airtable Personal Access Token credential.
- Add a Groq API credential for the chat model used to generate the structured onboarding checklist and summary.
- Add Gmail OAuth2, Trello, and Slack credentials, and set the Trello list ID plus Slack channel IDs (sales and manager) in the configuration values.
- Set the shared secret token, Airtable base ID/table name, high-value threshold, and stale-days threshold/cutoff logic in the configuration nodes.
- Copy the webhook URL from the webhook trigger and configure it in your e-signature tool, ensuring it sends the shared secret header/value expected by the workflow.