Daily tech stack signal alerts for Salesforce target accounts

Every weekday at 7am in my timezone, run a tech stack displacement watch over my Salesforce target accounts and ping the right AE in Slack the moment a meaningful change shows up. Trigger is a cron schedule. Workflow type is agent because the value is in the judgement call about which stack changes are real buying signals and in drafting the per account outreach angle.

Step 1. Pull my live target account list out of Salesforce using Get Many Accounts. Use a SOQL filter that returns accounts with an open opportunity OR a Tier 1 named account flag. For each account include the account Id, Name, Website, and OwnerId. Skip accounts with no Website because BuiltWith needs a domain.

Step 2. For each account's domain, call BuiltWith's Change API for Technology Additions and Removals over the last 24 hours to see what was added or dropped. If the change list is sparse or ambiguous, fall back to BuiltWith's Domain API Lookup for a fuller picture of the current stack so you can reason about context.

Step 3. Reason over each change and only escalate the ones that actually matter for a seller. The signal bar is: (a) a direct competitor of ours shows up on the account, (b) our own product category is removed, or (c) a clearly complementary tool is adopted that opens a new pitch angle. Drop everything else. Treat routine analytics or CMS swaps as noise unless they fit one of those three buckets. Ask me up front for my competitor list, my own product category, and the complementary tools that should count as signals, and persist those so I do not have to repeat myself.

Step 4. For each signal that survives, post a focused Slack Send a Message into a channel called #target-account-signals (let me change the channel during setup). Tag the Salesforce account owner so it lands on the right rep. The message should be one tight paragraph that names the account, names the change, says in one sentence why it matters for our sale, and proposes a copy-paste outreach angle the AE can drop into their next touch. Use Slack mrkdwn formatting.

Step 5. If no target account has a meaningful change in a given run, post nothing. Silence is the correct output on a quiet day so the channel stays high signal.

Owner mapping: to tag the right Salesforce owner in Slack, ask me once for a mapping from Salesforce owner email or name to Slack user, and persist it. If you cannot resolve an owner to a Slack user, fall back to posting the message without a tag and prefix it with the owner's name in plain text so the team can still route it.

Keep the agent stateless across runs except for the configuration items it asks for up front (competitor list, product category, complementary tools, channel name, owner to Slack mapping). The 24 hour BuiltWith window is enough to avoid re-alerting on the same change.