Skip to main content

​
Connected accounts (OAuth)

Connect third-party services (for example Google, Slack, GitHub, Stripe, HubSpot, and other supported providers). GenieForge stores tokens securely, refreshes them, and keeps them out of chat. You describe which service staff or the app should use; GenieForge wires the connection so actions call the provider without pasted tokens. Build, including from a connected MCP client, can declare the provider and scopes. You still paste Client ID and Client Secret under App Settings → Connections → Integrations, then click Connect. Do not paste those secrets into chat.

​
How to verify

  1. Open App Settings → Connections → Integrations.
  2. Copy the OAuth Redirect URL into the provider’s authorized redirect URIs.
  3. Save Client ID / Client Secret (and scopes), then Connect.
  4. Run the path that should use the connection; confirm it works without secrets in chat.
  5. After a scope change, Connect again so new grants take effect.

​
Limits and notes

  • A Needs credentials badge means the provider is declared but Client ID / Secret are not saved yet. Configure, then Connect.
  • To change scopes later without re-entering credentials: Integrations → Configure, leave credentials blank, edit scopes, save (or ask Build to update scopes).
  • Do not paste access tokens into the conversation.
  • Export/import does not copy live OAuth connections; reconnect in the destination.
  • Provider availability can vary; if a provider is missing, ask support@genieforge.ai.
  • HIPAA-enabled apps cannot connect OAuth providers. Those services are not covered by a Business Associate Agreement.