Upsun supports native integrations with multiple services, first and foremost Git hosting services such as GitHub, GitLab, or Bitbucket.
You can continue to use those tools for your development workflow, and have Upsun environments created automatically for your pull requests and branches.
List active integrations
With the CLI, you can list all your active integrations using the following command:
You get output similar to the following:
Validate integrations
Once your integration has been configured, you can check that it’s working as expected.
To do so, follow these steps:
-
Run the
upsun integration:validate command.
-
When prompted, select the integration you want to validate:
You get output similar to:
Debug integrations
When integrations run, they trigger “activities.” Activities are actions that happen on Upsun, and they get logged.
Usually these are triggered nearly instantaneously on the webhook endpoint.
These activities may be delayed due to the external services having latency.
Those logs are available via the CLI.
In most cases they aren’t necessary but may be useful for debugging an integration if it is misbehaving for some reason.
There are a handful of CLI commands available, all under the integrations section.
List all activities
To list all the updates triggered by activities on a given project and integration,
follow these steps:
-
Run the
upsun integration:activities command.
-
When prompted, select an integration.
You get output similar to the following:
You may also specify an integration to display in the command line directly: upsun integration:activities c4opi5tjv3yfd.
The ID is an internal identifier for the activity event.
The Description field is an arbitrary string of text produced by the integration code.
The State and Result fields indicate if the activity completed successfully, failed for some reason, or is currently in progress.
See the --help output of the command for more options.
To show detailed information on a specific activity,
run the following command:
The -t option specifies that timestamps must be included in the display of the results.
You get output similar to the following:
That shows the full output of the activity, including timestamps.
That can be especially helpful if trying to determine why an integration isn’t behaving as expected.
See the --help output of the command for more options.
If you omit the activity ID (the second random-seeming string), the command will default to the most recent activity recorded. Last modified on May 27, 2026
