Chapter: Integrations overview

Integrations

Integrations overview

VentionDesk fetches data from the services you already work with, and sends through them. Every connection belongs to your workspace and uses your access at the provider — with exactly the rights you give it.

How to connect a service

  1. Open Operations › Sources and click “Add source” (owner only).
  2. Choose the provider. The dialog shows the same guide as the pages here, and below it the fields for the access.
  3. Enter the token and details and click “Check and save”. VentionDesk checks the access with a request to the provider and only saves once it succeeds.
  4. Then assign the projects: GitHub via the repository in the project, hosting providers via “Assign hosting” in the project’s deploy panel, error trackers under “Assign error source” in the “Analytics” tab. Vercel and Render assign projects themselves via the linked GitHub repository.
  5. For Stripe, Sentry, Bugsnag and Rollbar you also enter a webhook URL at the provider — see Webhooks.

VentionDesk stores secret details (tokens, keys, signing secrets) encrypted and never shows them again. When editing, the secret fields stay empty; leaving them empty means unchanged. Whether a source is really connected is shown under Operations › Sources — measured by the last request, not by the stored configuration.

All providers

Code

Hosting

Mail

Errors

Payment

Email through your own service

Without your own email connection, VentionDesk sends with the sender from Settings › Email sender. If you connect Postmark, Mailgun, Amazon SES or Resend, your workspace’s emails go out through your account and your sender address.

Tickets from your own sites

Contact forms, apps and servers submit tickets without a connection via the ticket intake.

Integrations overview | VentionDesk Docs