Trigger Workflows on Document and Contract Status in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Documents & Contracts workflow trigger in Sparkforge fires when a document is sent, viewed, signed, or completed. Filter by template, recipient type, status, or contract value to scope automations precisely.

The Documents & Contracts trigger ties your document lifecycle directly to your automation. Anytime a doc moves through a status — sent, viewed, signed/accepted, or completed — Sparkforge can kick off a workflow. Useful for proposals, NDAs, service agreements, internal approvals, and anything else you want to react to without checking the dashboard.

What you can automate

Status-based follow-up — reminder emails when a doc is viewed but not signed, thank-you sequences when it's signed.
CRM updates — push doc activity to contact records, Google Sheets, or Slack.
Targeted automation — filter by template name so only specific doc types trigger a workflow.
Internal alerts — DM the rep when a $25K proposal is signed so they can call before the customer second-guesses.
Personalized client comms — pull custom values from the doc or contact into the outgoing message.

How to configure the trigger

1. Open Automation

Click Automation in the left nav, then + Create Workflow in the top right. Choose Start from Scratch.

2. Add a new trigger

Click + Add New Trigger. Scroll to the Payments section and select Documents & Contracts.

3. Name it

Use a descriptive name (e.g., "Onboarding Contract Signed") so you can find this trigger later when you have a dozen workflows.

4. Add filters

Click Add Filters to scope the trigger. Without filters, every doc event fires the workflow.

5. Filter fields

Filter	What it does
Recipient Type	Contact (external lead/client) or Business User (your team).
Status	Sent, Viewed, Signed/Accepted, Completed.
Template	Specific document or contract template.
Value	Contract amount; supports operators like Greater Than or Equals.

6. Save

Click Save Trigger. The workflow is now armed and will fire on matching events.

Practical patterns

High-ticket alert — Status: Signed/Accepted, Value > $5,000, Recipient Type: Contact. Slack alerts the closer immediately.
Stalled deal nudge — Status: Viewed, with a wait step and a check that signed status hasn't fired. Sends a friendly follow-up after 48 hours.
Onboarding kickoff — Status: Completed, Template: Service Agreement. Triggers welcome email and provisioning checklist.

Frequently Asked Questions

Can I run different workflows depending on whether a Contact or Business User signed?

Yes. The Recipient Type filter splits Contact and Business User events. Send a client onboarding email when a Contact signs and a Slack alert to ops when a Business User signs internal docs.

If a doc moves through multiple statuses, will the workflow fire each time?

Yes. Each status change is its own event. To avoid duplicate actions, use tags or custom-field checks inside the workflow before sending follow-ups.

Can I filter for high-ticket contracts only?

Yes. The Value filter supports Greater Than and Equals operators. Use it to fork high-value deals into a different sequence than smaller contracts.

How do I trigger a workflow only for one specific contract template?

Use the Template filter to pick the exact template. Service agreements can fire onboarding sequences while NDAs route to a different workflow.