Documentation / Reference
Integrations and limits
GitHub, Cloudflare, R2, email, Telegram, and current platform limits.
Connect providers in Settings
Provider credentials belong to the current private instance and are used by the platform. Keep them out of source code and public logs. The current instance is for approved GitHub accounts; integrations are not an isolated self-service account system for arbitrary public customers.
| Provider | Used for |
|---|---|
| GitHub App | Repository access, push deployments, and pull request previews |
| Cloudflare | DNS for accessible zones and R2 backup storage |
| Railway | Importing existing projects |
| Resend | Email notifications |
| Telegram bot | Chat notifications |
A provider card shows connection state and relevant errors. A connected DNS token does not by itself establish a successful backup: check R2 configuration and the backup history separately.
Email and your own sender
A Resend key with Sending access can send email but cannot list verified domains. Enter a sender on a domain already verified in Resend, for example alerts@example.com, when connecting or through Use your domain on the Email card. The existing API key can be reused.
With no custom sender, Upferry uses onboarding@resend.dev. The card shows Test sender, and mail can go only to the Resend account's email address. Verify your domain in Resend Domains, wait for Verified, then set your own sender in Upferry.
Upferry tests the sender before saving it. Acceptance by Resend is not proof of inbox delivery. Optional delivery tracking uses a Resend webhook: Full access can create it automatically; Sending access needs manual webhook setup and its signing secret. Check the last send, delivery event, and error on the card.