Who This Is For / When to Use
This article is for users building workflows that need to identify an existing contact before taking the next step, such as sending messages, updating records, creating opportunities, or handling external data like webhook payloads.
What the Find Contact Action Does
The Find Contact action automatically searches for an existing contact in Kyrios using one or more field values. When branching is enabled, the workflow splits into two paths so you can handle cases where a contact is found or not found separately.
This action reduces duplicate contacts and ensures downstream actions apply to the correct record.
How to Add the Find Contact Action to a Workflow
You add the Find Contact action from the workflow builder after choosing a trigger.
Steps:
Go to Automation → Workflows.
Click Create Workflow or open an existing workflow for editing.
Add a trigger, then click the + icon to add an action.
Select Find Contact from the action list.
Naming the Find Contact Action
The action name helps identify what the search is based on when reviewing workflows.
Use descriptive names such as Find Contact by Email or Find Contact by Customer ID to make workflows easier to maintain.
Selecting Fields to Match Contacts
The Find Contact action matches contacts using one or more fields you define. All selected fields must match for a contact to be found.
You can search using both standard and custom fields.
Standard Fields
Standard fields
include commonly used contact attributes such as Email, First Name, Last Name, Phone, Contact ID, and Contact Source.
Custom Fields
Custom Fields allow you to match contacts using data specific to your business, such as internal IDs, subscription details, or external references.
Adding Multiple Match Conditions
You can add multiple fields to refine the search. This is useful when a single field may not uniquely identify a contact.
Use Add field to include additional match conditions.
Enabling Branching for Find Contact
Branching allows the workflow to split into two clear paths based on whether a contact is found.
When enabled, Kyrios creates:
Contact Found branch
Contact Not Found branch
Each branch can contain different actions.
Confirming Branching Activation
When you enable branching, Kyrios asks for confirmation because this permanently changes the workflow structure.
Once confirmed, the workflow displays two separate branches under the Find Contact action.
Testing the Find Contact Action
Testing ensures the action behaves correctly before publishing the workflow.
Use Test Workflow to run a contact through the workflow and confirm whether the correct branch executes.
Common Use Cases
Preventing Duplicate Contacts
Search for an existing contact before creating a new one.
Webhook Data Matching
Match external identifiers such as a Stripe Customer ID stored in a custom field.
Conditional Messaging
Send different messages depending on whether the contact already exists.
Onboarding Workflows
Route new signups differently from existing customers.
Common Issues and Fixes
Contact not found when expected
Verify field values match exactly and that the correct field type is selected.
Multiple contacts match unexpectedly
Add additional fields to narrow the search criteria.
Branching not visible
Confirm branching is enabled and saved for the Find Contact action.