CRM
Stitch Subsidiary Accounts to Parent Companies in Salesforce
Nightly job that finds Salesforce accounts whose legal entity or domain matches a known corporate family and sets their ParentId.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionPull recently modified accounts from SalesforceSalesforce
- ActionResolve ultimate parent from Snowflake family tableSnowflake
- LogicBranch on confident match vs ambiguous
- ActionBulk-update ParentId in SalesforceSalesforce
- OutputPost link/conflict summary to SlackSlack
What it does
This workflow walks your Salesforce accounts every night, groups them into corporate families by matching email domains and normalized legal names against a reference table in Snowflake, and writes the correct ParentId on each subsidiary so the account tree reflects who actually owns whom.
When to use it
Run this when your account list has grown through inbound signups, imports, or acquisitions and the parent/child relationships are blank or wrong. Sales leadership wants whitespace and account-plan rollups that only work if subsidiaries roll up to the true parent.
How it works
- 1A nightly schedule fires the run.
- 2Pull all accounts modified in the last 48 hours from Salesforce, plus their domains and billing country.
- 3Query Snowflake's corporate-family reference table to resolve each account's ultimate parent DUNS or entity ID.
- 4Branch: if a confident parent match exists and differs from the current ParentId, queue an update; if ambiguous, route to a review list.
- 5Write the new ParentId values back to Salesforce in bulk.
- 6Post a Slack summary of links made, conflicts skipped, and accounts needing human review.
Set it up
What you configure once, before turning it on.
- 1Connect SalesforceAccounts, opportunities, cases.
- 2Connect SnowflakeWarehouses, queries, shares.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More CRM workflows
Dormant Account Check-In Call Scheduler
On the anniversary of an account's last touch, books a tentative check-in call on the owner's Google Calendar and emails the contact a scheduling invite.
Weekly Dormant-Anniversary Cohort Digest
Every week, groups dormant Attio accounts by which last-touch anniversary they hit that week, builds a prioritized digest.
AI-Personalized Dormant Account Win-Back
On a dormancy anniversary, an agent researches the account's history and recent public signals, drafts a genuinely personalized win-back email.
Backfill Intercom conversation topics onto stale HubSpot contacts
Finds HubSpot contacts with no recent Intercom topic, pulls their conversation history from Intercom, classifies the dominant topic with OpenAI.
Daily orphaned-opportunity sweep with manager Slack digest
Each morning this scans Salesforce for open opportunities owned by inactive users and posts a per-manager digest in Slack listing the orphaned deals that need a new owner.
Tag closed Intercom conversations onto Salesforce contacts in real time
On each Intercom conversation close, classifies the topic with OpenAI and appends it to the matching Salesforce contact's activity timeline so the topic never goes stale…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.