SOCIAL MEDIA
Open a Zendesk ticket from angry social mentions
Detects negative public mentions of your brand, opens a prioritized Zendesk ticket for each one, and alerts the on-call support lead in Slack so complaints get a real response.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled scrape of brand mentionsApify
- ActionScore sentiment and severityOpenAI
- LogicKeep only negative mentions
- ActionCreate prioritized Zendesk ticketZendesk
- OutputAlert on-call support lead in SlackSlack
What it does
This workflow turns public complaints into tracked support tickets. When someone posts something negative about your brand on social media, it creates a Zendesk ticket with the post content and a priority based on how severe the language is, then pings the support lead.
When to use it
Use it when social complaints slip through the cracks because they live outside your helpdesk. Turning each one into a ticket gives support a queue, an SLA, and an audit trail instead of a scroll-back through a feed.
How it works
- 1A schedule triggers an Apify scrape of recent public mentions of your brand handles and keywords.
- 2An OpenAI call scores each mention's sentiment and assigns a severity from low to urgent.
- 3A filter drops anything that is not negative so only real complaints continue.
- 4A Zendesk ticket is created with the post text, author, link, and mapped priority.
- 5A Slack message notifies the on-call support lead with the ticket link.
Set it up
What you configure once, before turning it on.
- 1Connect ApifyActors, scrapers, datasets.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ZendeskTickets, queues, knowledge base.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.