SOCIAL MEDIA
Archive impersonation evidence to R2 and alert the brand channel
Captures a tamper-evident evidence bundle (screenshot, page snapshot, metadata hash) for each newly flagged impersonator profile, stores it durably in Cloudflare R2.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled detection pass
- ActionPull flagged impersonator profilesApify
- ActionCapture screenshot and HTML snapshotBrowserbase
- ActionHash capture and build evidence manifestShell
- ActionUpload evidence bundle to dated R2 prefixCloudflare R2
- OutputPost Discord alert with hash and permalinkDiscord
What it does
It builds a durable, time-stamped evidence record for every impersonator your detection finds, so that when you file a takedown the proof still exists even after the fake account is deleted. Each bundle lands in R2 and the team gets a Discord ping linking to it.
When to use it
Use this when platforms or legal counsel demand preserved evidence at the moment of detection, since impersonators often vanish before a manual report is filed. It fits brand-protection and legal-ops teams building a defensible takedown trail.
How it works
- 1A schedule triggers a fresh detection pass.
- 2Apify pulls the latest flagged impersonator profiles from your monitoring source.
- 3Browserbase captures a full-page screenshot and HTML snapshot of each profile.
- 4A shell step computes a SHA-256 hash and writes a metadata manifest binding the capture to a timestamp.
- 5The screenshot, snapshot, and manifest are uploaded to a dated R2 prefix.
- 6Discord posts an alert per profile with the handle, hash, and R2 permalink.
Set it up
What you configure once, before turning it on.
- 1Connect ApifyActors, scrapers, datasets.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect ShellRun sandboxed commands inside the workspace.
- 4Connect Cloudflare R2Object storage, S3-compatible.
- 5Connect DiscordCommunity channels + voice + bots.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, 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.