The Estimates Workflow Trigger and Action

What This Trigger and Action Do

The Estimates workflow trigger lets you start automation when estimate activity occurs (like status updates). Pair it with the Send Estimate workflow action to automatically send an estimate to a contact or create it as a draft.

Key Features and Benefits

• Status-based automation: Branch logic for “Viewed,” “Accepted,” “Declined,” and more.
• Cleaner operations: Reduce manual sending and internal chasing.
• Better follow-up timing: Trigger tasks or messages as soon as the client engages.
• Flexible setup: Use filters + If/Else to keep enrollments precise.

Step-by-Step: Build an Estimate Workflow

1. Open Workflows
   Go to Automation → Workflows, then create a new workflow (or open an existing one).
2. Add the “Estimates” trigger
   Add a trigger and select Estimates from the trigger list.
3. Configure filters (recommended)
   Use filters to control what should start the workflow. Common filters include:
   • Status: Accepted, Declined, Invoiced, Sent, Viewed
   • Template: Target a specific estimate template
   • Value/amount: Route high-value proposals differently
4. Add the “Send Estimate” action
   Click the + to add an action → choose Send Estimate → select the user/template and sending mode:
   • Send directly (automatically sends the estimate)
   • Create as draft (creates an estimate for review before sending)
5. Save, publish, and test
   Publish the workflow and run a test estimate to confirm the trigger fires and actions behave as expected.

Status-Based Automation Ideas

Use If/Else conditions to run different follow-ups based on estimate status. Here are practical paths you can implement:

Common Use Cases

• Automatically send estimates after a form is submitted (paired with upstream triggers)
• Follow-up sequences if a client views but doesn’t accept
• High-value estimate routing to an internal approval step
• Onboarding workflows triggered when an estimate is accepted
• Seasonal services (renewals, upsells, annual maintenance)

Pro Tips

• Keep triggers filtered so you don’t accidentally automate every estimate in the account.
• Use tags to mark lifecycle stages (e.g., “Estimate Sent,” “Estimate Accepted”).
• When you add new branches, test with a single contact first to avoid looping behavior.
• Pair “Viewed” follow-ups with tasks so a real human can jump in at the right time.