The workflow builder supports more than simple one-trigger, one-action rules.

By combining conditional logic, split paths, and multi-step sequences, you can build workflows that mirror the full complexity of how your business qualifies and acts on leads.

This article shows how the advanced builder features work and provides real examples of what you can build with them.

Advanced builder features

AND/OR logic in filters

By default, every rule you add to a filter block uses AND logic.

All conditions must be true for the call to proceed.

You can switch any filter block to OR logic, so the call proceeds if any of the conditions are met.

To switch a filter block from AND to OR:

• Click the + button in the workflow builder.
• Select Add filter.
• Click the three-dot menu on the filter block.
• Select Set condition.
• Click + Add rule and add your criteria.
• Hover over the Logic: AND button.
• Click it to toggle it to Logic: OR.

This is useful when you want a workflow to fire for calls from multiple sources without creating two separate workflows.

True/false branching

True/false logic lets you define two separate paths in a single workflow.

One path for when a condition is met, and another for when it isn't.

This replaces the need for two separate workflows that cover opposite outcomes.

To add a true/false branch:

• Click the + button in the workflow builder.
• Select Add filter.
• Click the three-dot menu on the filter block.
• Select Set condition.
• Use the + buttons under the True and False branches to add the filters and actions for each outcome.

Split paths

Split paths let you run multiple independent action sequences from the same trigger, without creating separate workflows.

Each path can have its own filters and actions.

To add a split path:

• Click the + button directly under the Trigger block.
• Select Add path.
• Build out each path with its own filters and actions.

Multi-step sequences

You can chain as many filter and action steps as you need within a single path.

Each step runs in order after the previous one completes.

There is no limit on the number of filters, AI actions, or integration tasks you can stack.

AI orchestration

With AI orchestration, you can pair multiple AI workflows with other actions, all under a single workflow.

This lets you combine transcription, summarisation, AI tagging, and integration actions in one flow without managing them separately.

Example workflows

Example 1. Qualify leads and route to Google Ads automatically

Scenario: You want to send a conversion to Google Ads, but only for answered calls longer than 60 seconds from first-time callers.

All other calls should still be transcribed for review.

Setup:

• Trigger: Inbound call > Call ends

Path 1 - Qualified lead:

• Filter: Call outcome = Answered
• Filter: Call duration > 60 seconds
• Filter: 1st time caller = Yes
• Action: Google Ads (send conversion)
• Action: Transcribe call

Path 2 - All other calls:

• Action: Transcribe call

Using split paths keeps both sequences in one workflow and ensures every call is transcribed regardless of whether it qualifies as a conversion.

Example 2. Handle missed first-time callers with a callback tag

Scenario: Whenever a first-time caller doesn't get through, you want to flag them for follow-up by tagging the call and sending a Slack alert to your team.

Setup:

• Trigger: Inbound call > Call ends
• Filter: 1st time caller = Yes

True/false branch on Call outcome = Answered:

• True (call was answered): no further action needed
• False (call was not answered):
• Action: Update field > Tag > Callback Requested
• Action: Slack (send alert)

This uses a single true/false branch to act only on the missed leg while keeping the workflow compact.

Example 3. AI-powered lead scoring with CRM sync

Scenario: After every inbound call over 30 seconds, you want Nimbata AI to transcribe the call, generate a summary, assign a sentiment tag, and then push the record to HubSpot, but only if the AI tags the call as a qualified lead.

Setup:

• Trigger: Inbound call > Call ends
• Filter: Call duration > 30 seconds
• Action: Transcribe call
• Action: Summarise call
• Action: Update field > Tag > Fill with AI (instruct AI to apply Qualified Lead if the caller expressed buying intent)

True/false branch on Tag = Qualified Lead:

• True: Action: HubSpot (create or update contact)
• False: no further action

The AI tagging step runs first, and the HubSpot sync only fires if the AI confirms the call qualifies.

This keeps your CRM clean without requiring manual review of every call.

Example 4. Multi-platform attribution with per-source conversion routing

Scenario: You run campaigns across Google Ads and Meta. You want each platform to receive only its own conversions, and all calls should be transcribed.

Setup:

• Trigger: Inbound call > Call ends
• Filter: Call duration > 45 seconds

Split into three paths:

Path 1. Google Ads:

• Filter: UTM medium = cpc AND UTM source = google
• Action: Google Ads (send conversion)
• Action: Transcribe call

Path 2. Meta:

• Filter: UTM source = facebook_ads OR UTM source = instagram
• Action: Facebook (send call event)
• Action: Transcribe call

Path 3. Everything else:

• Action: Transcribe call

Using AND/OR logic within the filter blocks lets you match each platform's UTM patterns precisely.

The split path structure ensures a call attributed to Google Ads never accidentally fires the Meta action.

Example 5. Escalation workflow for repeat missed callers

Scenario: If the same caller has been missed more than once, you want Nimbata to tag them as a high-priority follow-up and notify a specific team member by email.

Setup:

• Trigger: Inbound call > Call ends
• Filter: Call outcome = Not answered
• Filter: Times called > 1
• Action: Update field > Tag > Callback Requested
• Action: Email notification (send alert to team member)

The Times called filter counts how many times that caller's number has called within the look-back window.

Combined with the not-answered filter, this workflow only fires when a caller has genuinely tried multiple times and been missed each time.

A combined example

The workflow below combines AND/OR logic, true/false branching, multi-step sequences, and AI orchestration in a single flow.

Whenever a first-time caller is not answered, a callback call flow is activated.

If the callback is answered, AI tags the call as a conversion.

If it is not answered, AI tags the caller as churned.

Detailed guide: How to set up your first workflow

Detailed guide: Workflow rules and tasks: what's available and how they work

Detailed guide: Workflow order and firing logic

Updated on: 03/04/2026