Every use case on this page is tied to a released connector or route family. Ads flows focus on faster campaign refreshes, while non-ads flows focus on delivery, enrichment, and routing.
| Family | Released integrations | Primary outcome |
|---|---|---|
| Ads activation | Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads, Microsoft Ads, Snapchat Ads, and Pinterest Ads | Refresh audiences and keyword targeting with preview and approval controls. |
| Commerce + paid conversion | Shopify and Reddit Ads | Push live demand context into storefront experiences and paid-conversion delivery flows. |
| Data destinations | BigQuery and Google Sheets | Land trend and workflow outputs in reporting systems your team already trusts. |
| Automation + routing | n8n, Slack, and generic webhooks | Route alerts and approved events into workflow runners, channels, and downstream systems. |
Use one-click ads connectors to turn live demand shifts into safer audience and keyword refresh workflows.
Map a positive trend category to a connected campaign entity, preview additive targeting updates, then apply only when the safety gates pass.
Keep separate brands, clients, or campaign groups isolated while still operating from one integration layer.
These flows turn trend signals into storefront context or paid-conversion delivery instead of direct ad-account edits.
Persist trend context to a mapped Shopify product via automated selection rules so storefront or app logic can react to live demand shifts.
Route saved conversion defaults and event overrides into the Reddit Ads connector when a campaign or measurement workflow needs explicit event pushes.
Use destination connectors when the primary job is to land operational or analytical rows in a system your team already trusts.
Ship trend or automation rows into a selected BigQuery table for analytics, QA, and downstream modeling.
Use Google Sheets when operators need human-readable row output with low-friction review, annotation, or approval workflows.
Routing connectors are for handoff. Use them when the next step belongs in an automation runner, alert channel, or signed endpoint your team already operates.
Connect a live n8n instance, pick a workflow or webhook target, and push release-approved trend events into a low-code automation runner.
Connect Slack once, select a destination channel, and keep incident or trend notifications in the workspace where operators already triage work.
Use generic webhooks when the destination is custom: Lambda, internal services, incident tools, CRM automation, or any POST-capable endpoint.
Released docs links for the live integration surface today: Shopify, Reddit Ads, BigQuery, Google Sheets, n8n, Slack, and generic webhooks.
This page only covers integrations currently released and working in production, so teams can evaluate live workflows without mixing them with reference-only endpoints.