Stand up Addepar households from every closed-won Salesforce deal

By General Input

Every hour, spin up the matching Addepar household the moment a Salesforce opportunity closes so ops isn't stuck creating client records by hand.

Integrations

  • Addepar
  • Salesforce
  • Slack

Type

Agentic Task

Categories

  • Operations
  • Sales

Every hour on the hour, watch Salesforce for opportunities that just flipped to Closed Won and stand up the matching client household in Addepar so the ops team stops creating records by hand after every signed deal.

Pull eligible deals from Salesforce with Get Many Opportunities filtered by StageName = 'Closed Won' and LastModifiedDate within the last hour. For each opportunity, use Get Many Accounts to fetch the linked account, primary contacts, and any onboarding-relevant custom fields you need to seed the client record. If the designated Addepar entity ID custom field on the opportunity is already populated, skip that opportunity — it was created on a previous run and re-creating it would duplicate the household.

For each opportunity that still needs onboarding, call Addepar List Entity Types to confirm the required attributes for the firm's household entity type. Then call Create Entity to add the household with the name, primary owner, and custom attributes mapped from the Salesforce account and opportunity fields. If the opportunity line items describe sub-entities such as individual brokerage accounts, joint accounts, or trusts, call Create Entity again for each of them and attach them under the parent household.

Immediately after a household is created, use Salesforce Update Opportunity to write the new Addepar entity ID back into the designated custom field on the opportunity. This is the load-bearing idempotency step — retries, partial failures, and duplicate cron runs all rely on that field being present to short-circuit.

Once the hour's batch is processed, post a single card to the onboarding Slack channel with Send a Message. List every household you created with its new Addepar entity ID, and separately list any opportunities that failed validation (missing required attributes, ambiguous entity type, unresolvable owner, etc.) so ops can pick them up manually. If nothing closed in the last hour, skip the Slack post.

Use judgment when choosing the entity type from List Entity Types — household vs individual vs trust depends on what the Salesforce account and opportunity fields describe. When a required Addepar attribute is missing or the entity type is ambiguous, do not guess: skip that opportunity and flag it in the Slack card. This workflow requires the ENTITIES_WRITE scope on Addepar and read plus field-update access on Salesforce Opportunity and Account.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentWin back LiveChat visitors whose chats went unansweredChat quality review board for LiveChat support leadsWin back no-show and cancelled appointments every morningLive Loop returns analytics with product-level drill-downNewsletter pre-flight and approval board for Mailjet sendsTurn a prospect spreadsheet into personalized sequence enrollmentsMailjet email delivery lookup console for support teamsCatch feature flags that never got switched on in productionA website visitor queue that remembers what you hide