Skip to main content
Job: encode the way your team finds, enriches, routes, and exports customers so an agent or scheduled job can run it again. Start from the business decision, not the provider.

Example: custom waterfall

You have LinkedIn URLs. You want a verified work email. You want to try your preferred path first and stop when the answer is good enough. The workflow shape:
  1. Read each lead.
  2. Run a person-to-email workflow.
  3. Verify the result.
  4. Export rows that need review.
The technical parts are there to keep the business process reliable:

Example: route by customer type

You search companies once a week. Directors and VPs should not get the same follow-up.
This is where custom workflows pay off. The workflow reflects your GTM motion, not a generic enrichment recipe.

Example: weekly search to Salesforce

You want new matching companies every Monday, enriched and pushed to Salesforce.

When to write a workflow

Write one when you need:
  • a custom provider order
  • different paths for different customer types
  • a weekly or daily run
  • a webhook from another system
  • repeatable output for Salesforce, CSV, or dashboards
Use a prebuilt workflow when you just need the standard answer once.

Add guardrails

Guardrails make background runs safer because they travel with the workflow.