Integrations

Social Listening Webhooks

Social listening is a use case spanning many providers rather than one app. FastHook provides a stable ingress and routing layer for mention, sentiment, keyword, and crisis alerts.

Capture the original request first, enforce the available trust boundary, then route and replay from durable evidence.

How the integration works

  • Providers expose different identifiers, author objects, sentiment labels, and delivery guarantees.
  • A normalized event can retain the raw provider payload while exposing common routing fields.
  • Deduplication should combine provider, network, post ID, and alert rule ID.
  • Urgent negative-sentiment alerts can route separately from routine reporting traffic.

Setup

  1. Create a provider source when FastHook supports its signature, otherwise use a secured custom WEBHOOK source.
  2. Map network, author, post URL, text, language, sentiment, reach, and rule identifiers.
  3. Route critical alerts to incident channels and routine mentions to storage or analytics.
  4. Replay only after confirming the receiver is idempotent.

Production notes

  • Respect platform terms, deletion events, and personal-data retention requirements.
  • Treat sentiment as a model output rather than an objective fact.
  • Do not create a SOCIAL_LISTENING source type because it is a category, not a signing provider.

Related documentation