Auto-enrich companies when a new Zoom account is created
When a new account is created in Zoom Admin, this workflow triggers instantly, extracts the company identifier (domain or name), enriches the account using Lusha’s Company API, and routes enriched firmographics into your CRM or database—so you standardize company data without manual research.
Why this works
New accounts often enter your systems with incomplete or inconsistent company fields. That creates downstream problems: messy routing, broken segmentation, manual enrichment tasks, and slow handoffs.
This play enriches at the moment the account is created—so every downstream workflow (assignment, scoring, onboarding, reporting) runs on consistent company intelligence from the start.
What you get
- Instant trigger when a Zoom Admin account is created
- Automated enrichment via Lusha Company API (industry, size, HQ, revenue range, funding stage, technologies where available)
- Structured output ready for CRM, Airtable/DB, Sheets, or Slack routing
- Cleaner data hygiene: dedupe, match rules, and ICP filtering before writing to your systems
How to set it up
Start from the Pipedream template
Open the template and create a workflow. It’s scaffolded with:
- Trigger: Zoom Admin — Account Created
- Action: Lusha — Company Enrich
Connect your Zoom Admin account (required)
In Pipedream:
- In the Zoom Admin trigger step, click Connect account
- Sign in with a Zoom admin (or an admin-approved service account)
- Approve the requested permissions/scopes
- Return to the trigger step and select the connected Zoom Admin account (the dropdown will populate once the connection exists)
Configure the trigger settings
Once the Zoom Admin account is connected:
- Choose the relevant account / org context (if prompted)
- Confirm the trigger event type is Account Created
- Generate a test event (or use a recent creation event if available) so downstream steps can map fields reliably
Map the company identifier for enrichment
Decide what you’ll enrich by:
Best option: domain
- Extract a domain from the Zoom account payload (if present)
- If it’s missing, derive it from an admin email domain (when appropriate)
Fallback: company name
- Use account name from the Zoom event payload
- Add basic cleanup (strip “Inc”, “Ltd”, punctuation) to improve match quality
Then map that identifier into the Lusha Company Enrich step.
Route the enriched result to your destination
Pick your write-back target:
- CRM (Salesforce/HubSpot): create or update Account record fields
- Database/Airtable: store enriched accounts for scoring + reporting
- Slack: alert when high-fit accounts are created
- Sheets: lightweight enrichment log for Ops review
Add guardrails (recommended)
Before writing to your CRM/DB, add logic to keep the workflow clean and cost-efficient:
- Deduplication: skip if domain already exists in CRM
- ICP filter: only write if employee count, region, or industry matches
- Error handling: if enrichment fails, send to a “Needs Review” table/channel
What to do next
- Auto-assign owners based on enriched region / segment
- Trigger onboarding workflows only for ICP-fit accounts
- Build a “new account intelligence” feed: Slack alerts + weekly recap
- Standardize data rules: one source of truth for industry/size/HQ fields
The goal: Every Zoom-created account should arrive in your systems already enriched and standardized—so routing, reporting, and outreach can start immediately, without Ops doing manual research.
No FAQ items available at this time.
Ready to build this?
Get started with Lusha and set up this play in minutes.
