This Workato workflow takes new Typeform leads and turns them into complete, enriched Salesforce records automatically. It sends each submission to Lusha for enrichment, uses an optional fallback provider if needed, updates Salesforce cleanly, routes the lead for a quick approval, adds approved prospects to Outreach, and notifies the team in Slack. The result is faster handoff, better visibility, and higher-quality inbound records without manual research or data cleanup.
Inbound leads should be the easiest part of your pipeline. Someone fills in a form, raises their hand, shows intent, and wants to hear from you. But in reality, this is where RevOps teams lose the most time: the CRM gets a name with no context, the SDR tries to guess the company, the manager chases a LinkedIn profile, and a lead that should reach sales in minutes ends up sitting in a queue for hours. The gap is not effort. It is missing data.
This is exactly where the steps in. Built for Workato and powered by Lusha, this workflow turns every new Typeform lead into a complete, enriched, and sales-ready record before your team ever touches it. And because it offers an optional fallback provider, you get the accuracy of Lusha with a safety net when a secondary source is needed.
This is the workflow RevOps teams try to build manually for years. Now it comes ready to deploy.
What this workflow solves
Every RevOps team runs into the same challenges:
- Empty or partial form fills
- Slow routing because SDRs cannot qualify what they cannot see
- Messy CRM inputs that weaken scoring and reporting
- Manual research that slows down response times
- Outreach sequences that underperform because they start with low-quality data
This Workato recipe removes that friction in one connected flow.
You get instant enrichment, clean upserts, a quick approval step, and automated enrollment into outreach sequences. It keeps your revenue engine moving without someone stopping their day to look up a prospect.
How the workflow works
This automation takes a new inbound lead from low-context to fully enriched and ready for outreach.
1. Typeform triggers Workato
A new submission enters your system. Even simple forms trigger the workflow immediately.
2. Enrich with Lusha
Workato sends the lead directly to Lusha. You may receive fields such as:
- Verified work email
- Direct phone number
- Current company
- Title and seniority
- Location
- Company size
- Industry
- Tech stack
- Funding data
- Revenue (where available)
This gives your team a real understanding of who is reaching out.
3. Optional fallback enrichment
If Lusha does not return a match, the record can go to a secondary provider. This gives you full coverage without lowering your standards.
4. Upsert into Salesforce
The enriched data is then added or updated in Salesforce. This keeps:
- Field mapping clean
- Duplicates under control
- Data aligned with your CRM structure
- Existing accounts accurate without losing valuable fields
5. Manual approval step
Before sending anything to Salesloft or Outreach, the record receives a quick internal review. Your team can approve, reject, or send it to nurture.
6. Send approved leads to Outreach
Approved records go straight into the correct sequence. SDRs do not need to search, tag, or manually enroll anything.
7. Notify the team in Slack
The workflow ends with full visibility. Your team knows who submitted the form, what enrichment returned, and where the lead was routed.
No spreadsheets, chasing, or missed prospects.
How teams use this every day
SDRs
Leads arrive enriched, reviewed, prioritized, and already enrolled in Outreach.
RevOps
No more broken field mapping, inconsistent scoring, or duplicates. The automation handles the logic.
Marketing
Form fills become more actionable, and the handoff to sales gets faster.
Managers
Clear visibility into inbound volume, quality, and follow-up without relying on manual checks.
Who benefits most from this workflow
This workflow is ideal for teams that want:
- Short, high-converting forms without losing context
- Consistent inbound qualification
- Faster handoff from marketing to sales
- Reliable Salesforce data
- Better adoption and performance in Outreach
- A waterfall enrichment model without building it manually
If your team has ever said “we do not trust the data coming in,” this solves that problem directly.
Setup tips
Teams that get the most from this workflow usually:
- Keep their forms short and let enrichment do the work
- Use fallback only when Lusha does not return a match
- Map titles, size, and industry into clear ICP tiers
- Use conditional updates in Workato to protect key fields
- Watch the Slack log as a live view of inbound quality
Deploy it once.
Improve every inbound touchpoint.
Turn your CRM into a system your team actually trusts.
Want to build your own inbound qualification flow?
Explore how Lusha’s API connects verified data, AI scoring, and automation tools like n8n to make RevOps faster, cleaner, and more predictable.
FAQs
This Workato recipe connects Typeform, Lusha, an optional fallback enrichment provider, Salesforce, Outreach, and Slack. It captures new Typeform leads, enriches them with Lusha, upserts them into Salesforce, routes them for manual approval, adds approved prospects to Outreach, and notifies the team in Slack.
The published template is built for Typeform as the trigger. If you use a different form tool, you can duplicate the recipe in Workato and replace the Typeform trigger with your own source, then keep the enrichment and routing logic.
This specific template is configured for Salesforce. If you use another CRM, you can adapt the logic in a copy of the recipe and change the upsert step to your system of record.
You need access to Lusha’s enrichment API and valid credentials so Workato can send leads for enrichment and receive the person and company data.
No. The template supports an optional fallback provider. You can keep it, replace it, or turn it off if you only want to use Lusha.
After enrichment and the Salesforce upsert, the template sends the lead to a manual approval step. Someone on your team reviews the record and either approves it for Outreach, rejects it, or sends it to another path you define.
The template uses an upsert step rather than a simple “create” step, so it is designed to update existing Salesforce records when a match is found. You can review and adjust the matching rules in Workato and Salesforce before going live.
Yes. You can edit the recipe and remove or bypass the approval step if you prefer fully automatic enrollment into Outreach sequences.
You should check your Salesforce field mappings, confirm which Outreach sequence or program new leads should enter, set the correct Slack channel for notifications, and decide whether to use a fallback enrichment provider.
SDRs can keep working from Salesforce and Outreach as usual. The workflow runs in the background and simply makes sure that new inbound leads arrive enriched, approved, and already enrolled in the right sequence.
