Setup
Setup
PULSE (Prescriptive Unified Lead & Social Engine) by Runink writes and publishes in your brand’s name, so it starts by learning who you are and which accounts it may read from or publish to. Each person does that under Settings. Some connections also need one-time work by the administrator of the PULSE instance in a platform’s developer console: those pages say exactly what to set.
Name, industry, timezone, language, tone, active channels.
Every card under Settings › Integrations, and what each one unlocks.
PULSE_PUBLIC_BASE_URL, the three sign-in callbacks, the TIDE edge.
META_APP_ID / META_APP_SECRET, permissions and app review.
One OAuth client: YouTube, Search Console, Gmail, Google sign-in.
LINKEDIN_CLIENT_ID / SECRET, products, company pages.
A fine-grained GitHub token for one repository; fixes as pull requests.
Each person’s own mailbox: Gmail, Microsoft 365 or SMTP.
TTSD_URL: TIDE’s shared speech service.
What needs which connection
| Feature | Needs |
|---|---|
| Brand Analysis (the audit, the diagnosis, content ideas), Campaigns, Studio drafts | Nothing: PULSE reads your public site and writes with its own model |
| Search demand in Brand Analysis and plans | Google Search Console |
| Publishing to Instagram, and reading its results, comments, mentions and messages | Meta |
| Publishing to YouTube, and reading its results and comments | |
| Publishing to LinkedIn, as yourself or a company page | |
| Fixes to your own website as pull requests | Website repository |
| Sending outreach email from your own address | |
| Voiceover on the Reels and Stories PULSE makes, read-back, podcasts | Voice |
| Lead sync and the WhatsApp sender allowlist | HubSpot, see Connections |
| Website traffic and forecasts | Google Analytics, see Connections |
| Ads performance | Google Ads, see Connections |
A connection never publishes by itself. Whether anything may leave PULSE is decided by the administrator’s switches; see Switches and arming order.