Brand Crisis Early Warning Workflow for Comms Teams

Build me an agent workflow that acts as a brand crisis early warning system. It should run on a cron trigger every 30 minutes.

Each run, the agent should call Talkwalker's Get Histogram (Project) operation twice against my configured brand project. The first call covers the trailing 1 hour window. The second call pulls a baseline for the same hour-of-day averaged over the previous 14 days. Both calls should return mention volume and sentiment breakdown so the agent can compare total volume and negative sentiment share between the two windows.

Compare current to baseline against two configurable thresholds: a volume spike threshold (for example, current volume more than 2x the baseline) and a negative sentiment share threshold (for example, negative share is more than 1.5x baseline AND above an absolute floor like 25%). If neither threshold is crossed, the workflow does nothing and exits quietly.

If either threshold is crossed, the agent should call Talkwalker's Search Project operation to pull the top driving mentions from the trailing hour, ranked by engagement or reach. From those mentions, the agent must identify the narrative: what people are actually saying, why volume is up, and which sources or authors are driving it. Do not just report that volume went up. The value here is the story, not the number.

Once the narrative is identified, the agent must do two things in parallel:

1. Post a Slack alert using the Send a Message operation into a designated crisis channel (configurable, default #crisis-comms). The message should include a short narrative summary, the top three driving links, a severity assessment (low / medium / high based on how far thresholds were exceeded and the share of negative sentiment), and a concrete suggested next step (for example: monitor for 1 hour, draft a holding statement, escalate to legal).

2. Create an Asana task using the Create a Task operation in the comms team's project, assigned to the on-call PR lead. Use the same narrative summary, top three links, severity, and suggested next step as the task description. Title the task with the severity and a short narrative slug, for example: "[HIGH] Negative spike about pricing change".

Configurable inputs the workflow should expose: Talkwalker project ID, volume spike multiplier, negative sentiment share threshold and absolute floor, baseline window size in days, target Slack channel, Asana workspace ID, Asana project ID, and Asana assignee (on-call PR lead). Anchor integration is Talkwalker. Companions are Slack and Asana.

Additional information

What does this prompt do?

Watches your Talkwalker project every 30 minutes for unusual spikes in mention volume or negative sentiment about your brand.
Compares the trailing hour against a 14 day baseline so normal chatter does not page anyone, only real anomalies do.
When a spike is detected, pulls the top driving mentions and writes a short narrative summary explaining what people are actually saying.
Posts a structured alert to your crisis Slack channel with the narrative, the top three driving links, a severity read, and a suggested next step.
Creates an Asana task assigned to the on call PR lead with the same context so the alert never gets lost in a busy channel.

What do I need to use this?

A Talkwalker account with a configured project that tracks your brand keywords.
A Slack workspace and a dedicated channel for crisis alerts, for example #crisis-comms.
An Asana workspace with a comms team project and an on call PR lead to assign tasks to.

How can I customize it?

Tune the spike thresholds for volume and negative sentiment share so you only get paged on real anomalies for your brand.
Change the cadence from every 30 minutes to every 15 minutes during a known high risk window like a launch day.
Swap which Slack channel receives alerts, and which Asana project and assignee owns follow up.

Frequently asked questions

Will this page my team for normal day to day chatter?

No. The workflow compares the last hour to a 14 day baseline of the same hour, so it only fires when current volume or negative sentiment meaningfully exceeds your normal pattern.

Why both Slack and Asana? Is one not enough?

Slack gives the team instant visibility, but crisis alerts often scroll past in busy channels. The Asana task creates accountable follow through with a named owner, so nothing falls through the cracks.

Can I change which keywords or topics it watches?

Yes. The workflow uses the topics and filters configured inside your Talkwalker project, so updating coverage is as simple as adjusting the project in Talkwalker.

What does the Slack alert actually look like?

It includes a short narrative of what people are saying and why, the top three driving links, a severity read, and a suggested next step so the on call lead can act immediately.

What happens when there is no spike?

Nothing. The workflow stays quiet and only posts when something genuinely unusual is happening, so your crisis channel signal stays high.