Integration boundaries
Distinguish account connectors, generated-app service calls, permission grants, and external billing.
On this page
Account connector or application dependency?
Account connections operate in the Rogue workflow: GitHub delivers code and Gmail can send a reviewed draft when available. A generated application's service dependencies are separate. Connecting Gmail to your Rogue account does not configure an email backend for every generated form.
| Surface | Verify |
|---|---|
| Account connection | Authorized account, granted scopes, connected state, and permitted action. |
| Application dependency | Destination endpoint, client or server execution, credential, quota, and billing account. |
| Catalogue item | Actual availability; Coming soon is not an active connection. |
Verify authorization and connection state
Use Preferences > Connections for the services offered to your account. Review the provider's authorization screen, then confirm the account and permissions shown after returning to Rogue. Availability and successful authorization are separate states.
On disconnection, read whether provider revocation was confirmed. If only the local connection was removed, complete revocation in the provider's account settings. A repository or an already sent message does not disappear when a connector is disconnected.
Gmail: draft, authorization, explicit send
For accounts with Gmail enabled, the conversation can produce a draft card. Inspect recipients, subject, and body before Send or Connect and send. The sending operation follows that explicit action. If the available action is Open in Gmail, delivery is completed outside Rogue rather than by a connected send operation.
Mailbox reading and search require separate availability and permission. Do not infer read access from send access or from signing in to Rogue with a Google account.
Generated-app service configuration
When App API keys is offered, use that interface for supported credentials. Managed calls can pass through Rogue's server so the provider key is not embedded in frontend code. That routing is a hosted runtime dependency; an exported static frontend does not implement it automatically.
Validate the service's real response and error behavior after configuration. Provider calls may consume that account's credits and quotas independently of Rogue usage. Key removal, revocation, or a provider quota can break an otherwise unchanged artifact.