Integrations
Connect Fly.io
New releases of your Fly apps appear as deployments in the projects.
Where to connect
In VentionDesk under Workspace › Sources › “Add source”, category Hosting, then Fly.io. Only the owner may connect, edit and remove.
Step by step
- Install flyctl and sign in with “fly auth login”. “fly orgs list” shows the short name of your organisation (e.g. personal).
- Create a read-only token with “fly tokens create readonly -o <organisation> -n VentionDesk”. VentionDesk does not need write access; a shorter expiry works with “-x 8760h”.
- Paste the whole output, including “FlyV1 ” at the beginning, and enter the short name of the organisation.
- Fly.io has no stable interface for the release history. VentionDesk therefore reads the machines of every assigned app every five minutes and records each new release version as a deployment — the history starts when you connect. Assignment happens on the project page under “Deploy” › “Assign hosting”.
What the dialog asks for
| Field | Entry | Where from |
|---|---|---|
| API token | Required | secret | In the terminal: fly tokens create readonly -o <organisation> — a read-only token for one organisation. Paste the whole output including “FlyV1 ”. |
| Organisation | Required | Short name of the organisation from fly orgs list, e.g. personal. |
VentionDesk stores secret entries encrypted and never shows them again. They are only saved once the provider confirms the access; if you edit a connection and leave a secret field empty, the previous value is kept.
All providers at a glance: IntegrationsWebhook URLs: Webhooks