If you’re asking questions like:
“Which step should I use for this use case?”
“What settings actually matter vs. what can I skip?”
“How do these steps work together in a real workflow?”
This doc is for you.
Each section explains when to use a step, what it’s best at, and how to configure it correctly, with examples pulled from common GTM workflows.
1. Account Data Enrichment
When to use
Use this step when you want to enrich an existing list of accounts with foundational firmographic data such as:
Company location
Employee headcount
Revenue
Industry
Website and domain details
This is typically one of the first steps in an account-based journey.
Steps
Add an Account Data Enrichment step to your journey.
Click Add Enrichment Param.
Choose one or more enrichment vendors.
You can select multiple sources to increase coverage.
Configure Required Fields:
Specify field names if you want waterfall behavior (enrichment stops once those fields are successfully filled).
Example
If you only care about employee_count and company_revenue, add those as required fields so Tapistro stops enriching once they’re found.
2. Account Job Enrichment
When to use
Use this step when you want to identify open job postings at target accounts.
Open roles often signal:
Active initiatives
Budget allocation
Internal pain or transformation
Example
A company hiring for a RevOps Leader may indicate an initiative to improve pipeline visibility or fix broken GTM processes.
Steps
Give your signal a name in Select Signal Tag.
Under Signal Type, choose Job Listings Search.
Fill out the Job Search Criteria:
Job Site: Select All (recommended for maximum coverage)
Include Job Title Patterns:
Enter a title
Press Enter after each one to add multiple titles
Exclude Job Title Patterns:
Example:
intern
Include Job Description Patterns:
Add keywords found inside job descriptions
Example phrase:
"We’re hiring a RevOps leader to help improve pipeline velocity"
→ Keyword to include:pipeline velocity
Technology To Include:
Specify tools or platforms mentioned in the role
Technology To Exclude:
Filter out irrelevant tech stacks
Job Posting Max Age (Days):
Example:
100days to exclude stale postings
Job Posting Min Age (Days):
Use if you want to ignore newly posted roles
Job Countries:
Specify hiring geographies
3. Person Data Enrichment
When to use
Use this step when you want to enrich a person list with basic contact details such as:
Email address
Location
Title
LinkedIn profile
Important note
Person Data Enrichment is already included inside the Person Search step.
The only reason to add this step after a Person Search is when you want to:
Pull additional data from LinkedIn for people you’ve already found
4. Person Search
When to use
Use this step when you want to find people that match:
Specific job titles
Keywords in their profile
A defined persona across multiple accounts
This is your primary step for building targeted prospect lists.
Steps
Configure a Persona:
Titles
Seniority
Keywords
Add a Search Source:
Choose where Tapistro should look for matching profiles
(Best Practice) Add an Email Validation step after Person Search:
Ensures higher deliverability
Reduces bounce risk before activation
5. TAP AI Agent
When to use
Use the TAP AI Agent when you want to replace manual research with AI-driven analysis.
Common use cases include:
Classifying accounts or people into defined categories
Determining whether a signal indicates real buying intent
Generating personalized outreach messages
The AI Agent can:
Read structured and unstructured data
Apply your logic consistently at scale
Output structured fields you can use downstream
Advanced Steps
These steps are powerful workflow controls that use expressions to filter or route accounts and people through a journey.
6. Data Filter
When to use
Use this step when you want to remove accounts or people from a workflow based on specific conditions.
Example use case
You want a Slack alert only when an account in your pipeline is showing a specific signal.
Workflow:
AI Agent researches whether the signal is present
Data Filter removes accounts where the signal is not present
Only qualified accounts continue to the Slack Alert destination
This keeps alerts highly relevant and noise-free.
Read more about configuring common Data Filters here: Data Filter Step in Tapistro Journeys | Tapistro Support Center
7. Conditional Branching
When to use
Use Conditional Branching when you want to fork your journey based on:
A specific field (e.g. location)
AI Agent output
Examples
Route US vs. non-US accounts into different activation paths
Branch based on AI output:
Has this account had a recent product launch? → Yes / No
Each branch can trigger different downstream steps, destinations, or messaging.
Final Tip
Start simple. Most high-performing journeys begin with:
List building (pull in an existing list or search for new accounts)
Basic Enrichment
AI Agents for advanced enrichment, signal tracking and classification
Filtering or branching
Destination
Once that foundation is solid, you can add advanced logic gradually as your use cases grow.