Connections
Settings › Integrations (/settings?tab=integrations) is one grid of
cards, one per account or channel. Publish to holds the places PULSE can
publish to; Measure & CRM holds the accounts it only reads. Every
credential is your own, stored per user and sealed (encrypted) before it is
written to the database. A card that needs the administrator to set something
first says which setting is missing.
How each one connects:
| Card | How you connect |
|---|---|
| Instagram, YouTube, LinkedIn | Sign in at the platform (OAuth): Connect with Instagram, Connect with YouTube, Connect with LinkedIn |
| Google Search Console | Sign in with Google (OAuth, read-only): Connect Search Console |
| Google Business Profile | Sign in with Google (OAuth, business.manage): Connect with Google, then choose the locations |
| Sign in with Google or Microsoft (OAuth), or your own SMTP server | |
| Website repository | A fine-grained GitHub token limited to that one repository, entered by an administrator |
| Website (blog publishing) | A GitHub token |
| Google Analytics, Google Ads | A Google Cloud service-account key you create |
| HubSpot | A HubSpot Private App token |
Publish to
LinkedIn, Instagram and YouTube
Each card offers Connect with LinkedIn, Connect with Instagram or Connect with YouTube when the administrator has set up the platform’s app (see LinkedIn, Meta, Google). You sign in at the platform and approve what PULSE asks for; PULSE stores the token, sealed, and renews it before it runs out where the platform allows. The card shows connected, expiring, expired, missing permission or not set up, the end date, and for each feature (publishing, results, comments, direct messages) whether the permission it needs was granted. Disconnect withdraws PULSE’s access at the platform where its API allows it, then deletes the stored tokens.
Fallback while sign-in is not set up. Until the administrator configures
the platform’s app, the card says sign-in is not set up and accepts a token
you created on the platform yourself. Test then asks the platform whose
token it is: LinkedIn GET /v2/userinfo (it needs the
openid and profile scopes, or the test fails with a 403) and Meta Graph
GET /me.
On LinkedIn you can post as yourself or, when the administrator turned on company pages, as a page you administer.
Website
Blog posts reach your website as a pull request, or a commit, made with a
GitHub personal access token stored on this card. The repository, branch and
folder are set by the administrator (PULSE_SITE_REPO and friends); see
Site pipeline.
Website repository
Your site’s own GitHub repository, where PULSE proposes fixes from the site audit as pull requests for you to review and merge. An administrator connects it with a token limited to that one repository. See Website repository.
Podcast and Audiobook
Episodes and chapters are published through PULSE’s own podcast feed, which podcast platforms poll. There is nothing to connect; the administrator sets the public address the feed needs.
Connect Gmail, Connect Microsoft 365 or an SMTP server: your own mailbox, so that Send on a lead’s email draft sends from your address. See Email.
Measure & CRM
Google Search Console
What people type into Google before they find your site. Connect Search Console signs in with Google, read-only, and PULSE reads clicks, impressions, click rate and position once a day. See Google.
Google Business Profile
Your Google reviews and Business Profile figures, drafted replies for your approval, posts you approve, and a review request proposed when you mark a deal won. Nothing is posted without your approval. See Google.
Google Analytics
Paste the full JSON key of a Google Cloud service account that has access to
the GA4 property, and the numeric Property ID (GA4 Admin › Property
Settings). Both are required. It feeds website traffic and the forecasts.
Without it, those places say Google Analytics isn't connected yet.
Google Ads
Paste the JSON key of a service account with domain-wide delegation (scope
adwords), the Ads Customer ID, a Developer Token, an optional
Login Customer ID (manager account), and the Subject email the service
account impersonates. All but the login customer ID are required.
Test on Google Analytics and Google Ads runs a real API call with PULSE’s own client.
HubSpot
A HubSpot Private App token. It enables Sync Now on Leads, pushes new prospects to HubSpot, and backs the WhatsApp sender allowlist (see Telephony and messaging).
Website form and SAM.gov
The website form gives you a link your site’s contact form can post to, so enquiries become leads. See Website form. SAM.gov takes your own API key so Leads can read US federal tenders.
PULSE has no connector for X (Twitter), Mailchimp or TikTok. Connections to them saved by older versions are hidden and never tested.
What Autopilot reads on Instagram and YouTube
Autopilot reads results, comments, mentions and direct messages back with the same token publishing uses. Each needs a permission on that token; PULSE never assumes one is granted. When a platform refuses a read for a missing permission, the account shows Reconnect to allow … for that kind only (the rest keeps working), and the reply queue says the same. To re-consent, connect again with the platform’s sign-in, which asks for every permission below, or paste a new token that has them (it replaces the old one).
| Platform | Kind | Permission / scope |
|---|---|---|
| Instagram (Graph API with Facebook Login: a Meta token and the Instagram professional account ID) | Results (reach, views, likes, comments, saves, shares where the post type reports them) | instagram_basic, instagram_manage_insights, pages_read_engagement, pages_show_list |
| Comments and replies; mentions (posts that tag the account) | instagram_basic, instagram_manage_comments, pages_read_engagement, pages_show_list | |
| Direct messages and replies | instagram_basic, instagram_manage_messages, pages_manage_metadata, pages_read_engagement, pages_show_list; the Instagram app setting Allow access to messages must be on | |
| YouTube (a Google access token and its refresh token) | Publishing | https://www.googleapis.com/auth/youtube.upload |
| Views, likes, comment counts; comments and replies | https://www.googleapis.com/auth/youtube.force-ssl | |
| Average view duration and percentage | https://www.googleapis.com/auth/yt-analytics.readonly |
Every Meta permission above needs Advanced Access through Meta App Review (and business verification) before it works for accounts that have no role on the Meta app. The three Google scopes are sensitive scopes: the instance’s OAuth client needs Google’s verification before people outside the project can grant them. A reply to a direct message is sent only within 24 hours of the person’s last message (Meta’s messaging window); after that PULSE says so and sends nothing. YouTube has no mentions and no direct messages: the app says “not available on YouTube”. A figure a platform did not report for that kind of post is shown as not measured, never as 0.