Retool
Connect Retool to Ploy to see everyone in your Retool organization, whether they are active or disabled, when they were last active, whether they use two-factor authentication, and who is in each permission group. Ploy can also create, disable and re-enable Retool users, and add and remove people on permission groups.
This integration is in beta
The Retool integration is in beta. It was built from Retool's API documentation and has not yet been checked against a live Retool organization, so some details may need adjusting once customers connect it. Beta does not limit what the integration can do.
The first step of setup is a consent checkbox. Ticking it lets Ploy capture redacted error data when a request to Retool fails: the error response Retool sends back, with personal details, tokens and other secrets removed. Ploy uses it only to fix problems with this integration. You must tick the box to continue.
What Ploy reads
Every user in the connected Retool organization, with their email address, name and when they joined
Whether each user is active or disabled. Disabled users lose their access in Ploy straight away
When each user was last active, and whether they have two-factor authentication turned on
Whether each user is a Retool admin
Every permission group, who is in it, and who is a group admin
Ploy does not read pending invitations, roles, access to individual apps, folders or resources, spaces, seat types or the audit log.
What Ploy can change
Create a user. From their email address, first name and last name. If an active user already has that email address, Ploy counts it as done.
Disable and re-enable a user. A disabled user can no longer sign in. Retool keeps the account, its groups and its history, so re-enabling restores their access.
Remove a person. Retool has no way to delete a user, so removing someone disables their Retool user, which ends their access.
Add or remove a person on a permission group. From the group's page in Ploy. Retool admins are members of the admin permission group, so this is also how admin access is given and taken.
Before you start
You need to be an admin of the Retool organization.
In Retool, open Settings, then API.
Create an access token. Give it the Users read and Groups read scopes so Ploy can see who has access.
If Ploy should make changes, also give it Users write and Groups write.
Copy the token. Retool shows it only once.
Each Retool space has its own address and its own token. To scan a space, create a token inside that space and add it as a separate connection.
Connect Retool
In Ploy, open Integrations, find Retool and click Connect.
Tick the beta consent checkbox.
Enter your Retool instance URL, the address you sign in to Retool at. For example
acme.retool.com, or your own address if you host Retool yourself.Paste the access token.
Click Test connection, then save.
Troubleshooting
Retool rejected that token: check the token was copied in full and has not been deleted from your organization's API settings.
That token cannot read your Retool users: give the token the Users read and Groups read scopes.
Retool could not be found at that address: check the instance URL. Enter only the address, for example
acme.retool.com, without a path.A change fails saying Retool refused it: give the token the Users write and Groups write scopes.
A self-hosted Retool cannot be reached: Ploy connects over HTTPS to addresses on the public internet only, so your Retool must be reachable from the internet with a valid certificate.