Workflow Automations

About

Workflow automations in Goliath let you build sequences that run automatically when specific events occur—“when X happens, do Y, then Z, then W.” Instead of relying on team members to remember every follow-up, task assignment, or outreach step, workflows ensure your playbook runs consistently every time. Common use cases include new-lead drip sequences, post-showing follow-ups, dormant-contact re-engagement, deal-stage-based internal handoffs (like assigning your transaction coordinator when a deal moves to Under Contract), and instant responses to property signals. With workflows, nothing falls through the cracks, and your team executes the same proven process for every opportunity.

What Workflows Can Do

Workflows are built from three core components: triggers, actions, and logic.

Triggers: What Starts a Workflow

A trigger is the event that launches your automation. Goliath supports a wide range of triggers to match real-world scenarios:

• A new contact is created
• A contact is added to a specific list
• A contact is tagged
• A deal changes stage
• A property signal is received (e.g., a tax delinquency alert for a tracked property)
• A form is submitted on your website
• An inbound message arrives (email or SMS)
• A scheduled time is reached (for recurring workflows)

Choose the trigger that aligns with the moment you want the automation to begin—whether that’s the instant a lead enters your system or when a deal milestone is achieved.

Actions: What the Workflow Does

Once triggered, a workflow executes one or more actions against the matched record. Available actions include:

• Send an email (personalized with contact or property merge fields)
• Send a text message (SMS) to the contact’s mobile number
• Create a task for yourself or a team member
• Assign a task to a specific user (useful for internal handoffs)
• Change a deal’s stage to move it through your pipeline
• Add or remove a tag to segment or organize contacts
• Add to a list for grouping or targeting
• Post to Slack to notify your team in real time
• Call a webhook to integrate with external systems
• Trigger another workflow to chain complex sequences

You can stack multiple actions in a single workflow to handle multi-step processes—like sending an email, waiting two days, then creating a follow-up task if the contact hasn’t replied.

Delays and Conditions: Spanning Time and Logic

Workflows aren’t limited to instant one-off actions. Delays let you space actions over time: “wait 2 days, then send the follow-up email,” or “wait 1 week, then check if the contact has responded.” Conditions add decision-making: “if the contact replied, stop the sequence; otherwise, send the next message.” This combination turns a simple automation into a sophisticated drip sequence that adapts to contact behavior and unfolds over days or weeks.

When to Use Workflows

New-Lead Drip Sequences

When a new contact is created or added to your acquisition list, launch a multi-touch email or SMS sequence introducing yourself, explaining your offer, and inviting a conversation. Space messages over several days to stay top-of-mind without overwhelming the recipient.

Post-Showing Follow-Ups

After scheduling a property showing (tracked via a deal stage or tag), trigger a workflow that sends a thank-you email the next day, creates a task to call the seller, and posts a Slack notification to your team.

Dormant-Contact Re-Engagement

Set up a workflow that fires when a contact hasn’t responded in 90 days. Send a re-engagement email, wait a week, then create a task for a phone call if no reply arrives.

Deal-Stage-Based Internal Handoffs

When a deal moves to Under Contract, automatically assign a task to your transaction coordinator, send a Slack notification to the team, and update internal tags—all without manual coordination.

Inbound-Signal Response

When a property signal hits for a contact on a tracked list (e.g., a tax lien is filed), immediately send the owner an SMS offering to help, then create a task to follow up in three days.

Managing Workflows

Workflows can be paused to temporarily stop new runs, resumed to reactivate them, edited to refine triggers or actions, and cloned to create variations for different lists or markets. When you edit a running workflow, the changes apply to future runs; contacts already in-flight continue on the version they started with, ensuring no one receives duplicate or conflicting messages.

Pro Tips

• Use conditions to branch workflows based on contact replies, deal stages, or tag presence—this prevents generic sequences from spamming engaged leads.
• Chain workflows together for complex playbooks: a “New Lead Intro” workflow can trigger a “Motivated Seller Deep Dive” workflow if the contact responds positively.
• Leverage delays strategically: a 2-day wait feels natural for follow-ups, while a 7-day pause works well for re-engagement.
• Test workflows on a small list first—verify emails render correctly, tasks assign to the right team members, and delays behave as expected before scaling up.

Frequently Asked Questions

Q: What happens if I edit a workflow that’s already running?

Changes to a workflow apply to new runs only. Contacts already in the middle of a sequence continue on the version they started with, so you won’t accidentally interrupt or duplicate messages.

Q: Can I stop a contact from receiving further messages in a workflow?

Yes—either pause the workflow entirely, or use a condition to check for a reply or tag (like “Do Not Contact”) and stop the sequence if present. You can also manually remove the contact from the triggering list.

Q: How do I know if a workflow triggered successfully?

Goliath tracks workflow runs and logs each action (email sent, task created, etc.) in the contact or deal activity timeline. You can review this history to confirm the sequence executed as designed.

Q: Can workflows trigger on weekends or outside business hours?

Yes—workflows run 24/7 based on the trigger and delay settings you configure. If you want to restrict sends to business hours, use a condition to check the current day/time before executing email or SMS actions.