Connect Resilio
The Resilio integration connects workflows to your Management Console over HTTPS. The integration is in beta and uses the API documentation for Resilio 6.0.4.1
Create an API token
In the Resilio Management Console, open Settings > API and select + Create new token. Associate the token with a dedicated account and grant only the permissions your workflows need. Copy the token.
2
Open the Resilio connection form
In Serval, add a Resilio connection from the integrations page.
3
Enter the Management Console host
Enter the HTTPS hostname and API port, for example
resilio.example.com:8446. Don’t include /api/v2 or another path. New Management Console installations use port 8446 for the scalable API. Upgraded instances can use a different port. Use the API port configured for your instance.4
Enter the token and connect
Paste the API token without the
Token prefix, then save the connection.5
Run the health checks
Run the connection, agent-list, and run-list checks. These checks read data from Resilio and don’t create or change jobs.
For a private Management Console, enable Run on self-hosted workers on the connection. The worker and its credential proxy must run a Serval release that includes the Resilio integration. Older workers can’t resolve credentials for this integration. The worker must reach the configured host and port and trust its TLS certificate.
Use Resilio in workflows
Use the Resilio API request action to call the Management Console API. Requests include the/api/v2 path prefix. The token stays in the connection. Serval adds it to requests for the configured host and port.
The available operations cover agents, groups, jobs, runs, users, schedules, storage, and other Management Console settings. Write operations require the corresponding Resilio permissions. Connecting doesn’t start a background sync or transfer.
The typed action supports JSON requests and responses. File uploads, report downloads, and support archive downloads aren’t supported.
Check the connection
The integration includes three health checks:- Validate API connection: reads Management Console information.
- List agents: requests one agent to check agent-read access.
- List runs: requests one run to check run-read access.

