Skip to Content
IntegrationsPublishing & Channels

Publishing and Channels

Brand credentials connect publishing destinations, communication channels, advertising accounts, and external content systems. OAuth credentials are created through Accounts → Add Account. API-key connectors ask for their provider values directly.

Credential-platform catalog

Registry keyIntegrationConnectionCurrent code-backed role
YOUTUBEYouTubeGoogle OAuthVideo publishing, channel data, analytics, and comments
INSTAGRAMInstagramMeta OAuthPublishing, account data, analytics, and comments
TIKTOKTikTokTikTok OAuthPublishing and account data
FACEBOOKFacebookMeta OAuthPage publishing and account access
GOOGLE_ADSGoogle AdsGoogle OAuthCampaign, account, and analytics operations
GOOGLE_SEARCH_CONSOLEGoogle Search ConsoleGoogle OAuthSearch property and performance reads
TWITTERX (Twitter)OAuth 2.0Account access, publishing, and social data
X_ADSX AdsOAuth 1.0a (three-legged)Ads account access, campaign, and analytics operations
LINKEDINLinkedInLinkedIn OAuthAccount access and publishing
PINTERESTPinterestPinterest OAuthPin publishing and analytics
REDDITRedditReddit OAuthAccount access and publishing
DISCORDDiscordDiscord OAuthOrganization bot and channel messaging
TELEGRAMTelegramBot tokenBot verification and distribution
TWITCHTwitchNot connectableReserved schema value; no active connect module
RESTREAMRestreamRestream OAuthMultistream chat ingest and live-session context
MEDIUMMediumMedium OAuthArticle publishing
THREADSThreadsMeta Threads OAuthText and media publishing
FANVUEFanvueFanvue OAuthCreator account access and publishing
SLACKSlackSlack OAuthWorkspace and channel messaging
WORDPRESSWordPress.comWordPress OAuthArticle publishing
SNAPCHATSnapchatSnapchat OAuthAccount access and publishing adapters
WHATSAPPWhatsApp via TwilioDeployment credentialsText, media, template messages, and delivery status
MASTODONMastodonDynamic OAuth per instanceFederated account access and publishing
GHOSTGhostAdmin API credentialArticle publishing
SHOPIFYShopifyShopify OAuthStore access and product publishing workflows
BEEHIIVBeehiivAPI keyPublication selection, newsletters, and subscribers
UNIPILEUnipileAPI key and DSNAccounts, messages, email, and calendar data
DEVTOdev.toAPI keyArticle publishing

The registry can contain a value before a user-facing connector is available. Twitch is explicitly documented as reserved so its presence is not mistaken for an implemented OAuth path.

Self-hosted OAuth applications

Self-hosted deployments must register their own provider applications and set the callback URI to the corresponding Genfeed verification route.

Google sign-in, YouTube, Google Ads, and Search Console share GOOGLE_OAUTH_CLIENT_ID and GOOGLE_OAUTH_CLIENT_SECRET. Their redirect URIs and API-specific credentials remain separate.

IntegrationServer configuration
YouTubeGOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET, YOUTUBE_REDIRECT_URI; optional YOUTUBE_API_KEY
InstagramINSTAGRAM_APP_ID, INSTAGRAM_APP_SECRET, INSTAGRAM_REDIRECT_URI
TikTokTIKTOK_CLIENT_KEY, TIKTOK_CLIENT_SECRET
Facebook / MetaFACEBOOK_APP_ID, FACEBOOK_APP_SECRET, FACEBOOK_REDIRECT_URI
XTWITTER_CLIENT_ID, TWITTER_CLIENT_SECRET, TWITTER_REDIRECT_URI; optional app-level bearer/consumer credentials
X AdsX_ADS_API_KEY, X_ADS_API_SECRET, X_ADS_REDIRECT_URI
LinkedInLINKEDIN_CLIENT_ID, LINKEDIN_CLIENT_SECRET, LINKEDIN_REDIRECT_URI
PinterestPINTEREST_CLIENT_ID, PINTEREST_CLIENT_SECRET, PINTEREST_REDIRECT_URI
RedditREDDIT_CLIENT_ID, REDDIT_CLIENT_SECRET, REDDIT_REDIRECT_URI, REDDIT_USER_AGENT
ThreadsTHREADS_CLIENT_ID, THREADS_CLIENT_SECRET, THREADS_REDIRECT_URI
MediumMEDIUM_CLIENT_ID, MEDIUM_CLIENT_SECRET, MEDIUM_REDIRECT_URI
FanvueFANVUE_CLIENT_ID, FANVUE_CLIENT_SECRET, FANVUE_REDIRECT_URI
WordPress.comWORDPRESS_CLIENT_ID, WORDPRESS_CLIENT_SECRET, WORDPRESS_REDIRECT_URI
SnapchatSNAPCHAT_CLIENT_ID, SNAPCHAT_CLIENT_SECRET, SNAPCHAT_REDIRECT_URI
DiscordDISCORD_CLIENT_ID, DISCORD_CLIENT_SECRET, DISCORD_REDIRECT_URI
SlackSLACK_CLIENT_ID, SLACK_CLIENT_SECRET, SLACK_REDIRECT_URI
Google AdsGOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET, GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_ADS_REDIRECT_URI
Google Search ConsoleGOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET, GOOGLE_SEARCH_CONSOLE_REDIRECT_URI
RestreamRESTREAM_CLIENT_ID, RESTREAM_CLIENT_SECRET, RESTREAM_REDIRECT_URI

Provider dashboards require an exact redirect URI match. Use the public API URL for the deployment; do not register localhost callbacks for production.

API-key and deployment connectors

  • Beehiiv and dev.to validate the submitted brand credential before saving it.
  • Ghost requires values that can produce a valid Ghost Admin API request.
  • Telegram validates the configured bot token.
  • WhatsApp uses the deployment’s Twilio account, token, and sending number.
  • Unipile accepts organization configuration and can fall back to deployment environment values.
  • Mastodon registers an OAuth application against the selected instance rather than assuming one global host.

Connection verification

  1. Connect the account from the intended brand.
  2. Verify the returned account or publication identity before publishing.
  3. Publish a private, draft, or otherwise low-impact test when supported.
  4. Confirm the provider returns its external ID and Genfeed records the result.
  5. Revoke test credentials that are not intended for continued use.
Last updated on
ArgilMessaging & Automation