Workflows in Kylas are designed to automate repetitive actions across the sales process. You can create custom rules using Triggers, Conditions, and Actions, allowing the system to automatically perform specific tasks when defined events occur. This not only reduces manual effort but also enhances productivity and consistency in operations.
In this scenario, we will demonstrate how to execute one workflow based on another, by chaining actions using field updates and then calling another workflow using the “Execute Another Workflow” action.
Permissions:
Any user with Basic access (Create) and Admin access (Read All and Update All workflows).
Product Plans:
Available in the Elevate and Exceed plan.
Activities to be Completed:
execute another workflow as a trigger
This workflow updates the Lead's pipeline stage.
CRM Settings → Automation → Workflows
Tap the “Add Workflow” button on the top right to create a new workflow
Workflow Name: Update lead stage to contacted (Example)
Description (optional): Update lead stage to contacted with another workflow is trigger.
Choose Entity = Lead
Action Type : Execute as an associated entity action
Trigger type: Immediate
Click Save & Activate to immediately enable the workflow
Or click Save to keep it in draft mode for later activation
Workflow 2: Trigger Pipeline Update via Call Log
Objective: Automatically update the lead pipeline stage when a call outcome is marked as "Connected."
CRM Settings → Automation → Workflows
Tap the “Add Workflow” button on the top right to create a new workflow
Workflow Name: Call Log (Example)
Choose Entity = Call Log
Action Type : When the call log is updated
Trigger type: Immediate
Field: Outcome
Operator: Equals
Value: Connected
Field: Execute Another Workflow
Target Entity: Associated Lead
Workflow to Execute: Update Lead Stage to Contacted (created in Workflow 1)
Click Save & Activate to immediately enable the workflow
Or click Save to keep it in draft mode for later activation
When a lead is updated to the “Won” stage:
A Deal, Contact, and Company are automatically created
Mappings and ownership are applied as per configuration
Converted entities will be visible in respective modules
Workflow trigger count will reflect on the workflow listing page
Check the workflow status to verify whether it was successfully triggered or not.