Configure integrations deliberately

Named connections and AI

1. Create a named connection of the correct type in Connections. Enter the provider’s actual endpoint and credentials.
2. Save, then run the explicit connection/model/tool discovery action. Review failures without repeatedly resubmitting a potentially chargeable operation.
3. For AI, load available models and select one actually offered. A custom label is not proof a model exists.
4. Activate the connection for site writing, select it for an agent, or bind its exact tool in Studio as separate actions.

Blank secret inputs normally retain the saved credential; use the explicit clear control when revoking it. On a stale-version conflict, reload and reconcile nonsecret settings. Never paste secrets into content or support screenshots.

Email: SMTP or Resend

In Email settings, choose the provider, configure its sender and save. Resend requires its API key and a verified sending domain; SMTP requires the correct host, port, security and authentication. GoRun’s test action sends a real message, so use an address you control.

Saving or probing settings does not prove delivery to an inbox. Confirm receipt and inspect the provider’s delivery status. Managed signup requires a configured working mail path; an activation request must not be treated as sent when no provider is configured.

• Resend: domain setup

S3 media and encrypted backups

Save and test the S3-compatible connection, then open Storage. Activating it for new media and for private encrypted backups are separate choices. A bucket connection does not migrate old files automatically.

• Keep the original destination available for existing media after a switch. Disabling a destination for new uploads does not remove its old files.
• Generated studio media is organized by site, content item and date. Media access rules still apply; a private bucket does not by itself make a published media URL private.
• Manual encrypted backups need a restore plan and the original site secret. Remote media in S3 needs its own bucket retention/backup strategy.

• Amazon S3 documentation
• Cloudflare R2 documentation

Stripe and service readiness

On GoCloud, payment configuration belongs to the hosting owner. Test and Live mode are separate; test invoices do not unlock paid benefits. Manual service approval is not proof of payment unless payment was explicitly confirmed.

Stripe Connect setup requires registered OAuth application details and its redirect URI before a client can connect. Connection consent alone does not configure the required webhook or complete a payment. The same platform account cannot connect to itself; use the supported manual configuration for that account.

Check the actual account, mode, webhook configuration and signed payment outcome. Do not promise a paid feature from a saved key or a successful connection test.

• Stripe Connect OAuth reference

Metricool draft delivery

Metricool has its own settings and per-site status summary. Configure and test that site’s connection, then explicitly create a draft. A delivery record is not a published social post; inspect the actual Metricool draft before scheduling publication.