KFC ThailandAgentsIntegrations

The crew

0 running

Every agent has a named job, a gate on every consequential move, and a ledger of what it did for whom.

Fabulate Agent Cloud connected16 sessions on record · 146 actions loggedBrandSync runs hourly for one brand; every other workspace runs it by handlast crew activity 08/09/2026 05:29
IntegrationsThe crew works in your tools1 connected · 4 ready and waiting on keys · 5 designed but not wired. 0 carry saved config.read from the server environment · key names only, never values

A card says “connected” only when the code for it exists here AND its keys are in the server environment. Nothing you type on this page can change that — which is the point.

SlackReady, needs its keys

The crew already lives where the team talks: a gate approved in Slack is the same decision as one approved here.

  • Briefs in, as a message to the crew
  • Gate cards out — approve in the thread
  • Daily digest to a bound channel
Bound channels#kfc-zinger · Zinger Double Down Dark · Launch#kfc-thailand · brand-wideManage bindings
set SLACK_BOT_TOKEN + SLACK_APP_TOKEN to switch on
NotionPlanned, not wired yet

Most brand rules and briefs are already written in Notion; reading them there beats re-typing them here.

  • Briefs in, from a brief database
  • Campaign wrap-ups out, as a page
  • Brand rules kept in sync
no adapter shipped yet
HubSpotPlanned, not wired yet

Client-side reporting lives in the CRM; the roster's stages are the same pipeline by another name.

  • Creator and agency contacts out
  • Deal stages synced from the roster
  • Campaign spend against the account
no adapter shipped yet
LinearPlanned, not wired yet

Production work is task work; the people doing it already have a board.

  • Production tasks out, one per deliverable
  • Compliance change-requests as issues
  • Status back onto the roster
no adapter shipped yet
Google DrivePlanned, not wired yet

Footage arrives in Drive whatever we build; the Media Hub should read it where it lands.

  • Creator submissions in
  • Approved cuts and stills out
  • Contract PDFs filed by campaign
no adapter shipped yet
WhatsApp BusinessReady, needs its keys

The default channel for reaching a creator directly — chosen over LINE for new work. Every send is still a gate.

  • Creator replies in
  • Approved outreach out
  • Agency/creator notifications out — offers, decisions, payments, reviews
set WHATSAPP_PHONE_NUMBER_ID + WHATSAPP_ACCESS_TOKEN + WHATSAPP_VERIFY_TOKEN + WHATSAPP_APP_SECRET to switch on
LINEReady, needs its keys

Kept for an existing LINE thread; new work defaults to WhatsApp. Hidden from the messaging UI entirely until a channel token is set. Every send is still a gate.

  • Creator replies in
  • Approved outreach out
  • Agency/creator notifications out — offers, decisions, payments, reviews
set LINE_CHANNEL_ACCESS_TOKEN to switch on
EmailReady, needs its keys

The channel of record for anything a lawyer might read later, and the one every agency user already has by default.

  • Outreach out, from the campaign address
  • Agency/creator notifications out — offers, decisions, payments, reviews
  • Client digests on a schedule
set RESEND_API_KEY to switch on
Culture signals · data layerConnected

BrandSync, Discovery and Content Intelligence read the same trends a human sees in Brand Intelligence, with the source and date on every row; nothing external is declared on the agents.

  • Trending hashtags, top content and posts by market and category
  • Press and video trends for the brand's market
  • Trends with a permission score computed from the brand's own rules and creatives
keys present ·
WebhookPlanned, not wired yet

The escape hatch: if we do not integrate with it, the ledger can still push to it.

  • Every settled action out, as JSON
  • Gate raised / gate decided events
  • Whatever your own stack needs
no adapter shipped yet