SOCIAL MEDIA
Triage customer-reported fake accounts from a webhook and escalate confirmed ones
Receives reports of suspected fake brand accounts via webhook, verifies each handle against your authentic-account registry and a live profile capture.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: customer reports a suspicious handleHTTP webhook
- LogicCheck handle against verified-account registry
- ActionCapture live profile of unknown handleBrowserbase
- ActionReturn authentic vs. impersonation verdictOpenAI
- LogicClose authentic, route confirmed fakes
- OutputOpen Front triage conversation with evidenceFront
What it does
It turns inbound "is this account really you?" reports into a fast, evidence-backed verdict. Authentic matches are auto-resolved; confirmed impersonators are escalated as a Front conversation so your support team can action the report and reply to the customer who flagged it.
When to use it
Use this when customers and partners regularly forward suspicious handles and your team wastes time eyeballing each one. It is ideal for support and brand-safety teams who want triage automated but human follow-up preserved.
How it works
- 1A webhook receives a reported handle and platform.
- 2A logic step checks the handle against your verified-account registry.
- 3For unknown handles, Browserbase loads the live profile and captures the bio, follower stats, and a screenshot.
- 4OpenAI compares the profile to your brand identity and returns an authentic-or-impersonation verdict with confidence.
- 5A logic branch closes authentic results and routes confirmed fakes onward.
- 6Front opens a triage conversation with the evidence so an agent can file the takedown and update the reporter.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect FrontShared inbox, conversations.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Social Media workflows
Discord event capacity gate with automatic waitlist promotion
Enforces a seat cap on RSVPs: once an event is full, new sign-ups join a waitlist, and when someone drops out the next person is promoted, notified in Discord.
Tiered Discord event reminder fan-out (24h / 1h / live)
On a schedule, scans upcoming Discord-tracked events and DMs each confirmed attendee staged reminders at 24 hours, 1 hour, and event start.
A/B carousel cover variants from one brief
Takes a single approved brief and uses an LLM to write three distinct cover-slide headlines, renders a carousel cover for each, and logs the variants to Airtable for an A/B test.
Localized carousel variants per target market
From one approved master brief, translates the copy into each target locale, renders a localized carousel per market, and publishes each to its region's platform account.
Carousel render and auto-publish on Slack approval
Renders carousel variants from a brief, posts a preview to Slack for a one-click approve, and on approval publishes the chosen variant to the connected social platforms.
Discord /rsvp slash command with Outlook calendar invite
Lets members RSVP to an event via a /rsvp slash command, captures their status (yes/maybe/no), and sends a matching Outlook calendar invitation or cancellation to their email.
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.