Prerequisites
- An Anypoint Platform organization on the US, EU, or Government Cloud control plane. Organizations on another MuleSoft cloud, on MuleSoft Government Cloud Plus, or on Private Cloud Edition can’t connect yet: contact us.
- The Organization Administrator permission in the business group where you create the Connected App. See MuleSoft’s Creating Connected Apps.
- The Admin role in your CloudThinker workspace, which can add and edit connections. See Roles.
Setup
Create a Connected App
cloudthinker, and select App acts on its own behalf (client credentials).Add scopes
Copy the client ID and secret
Add the connection in CloudThinker
Connection details
anypoint.mulesoft.com is US, and eu1.anypoint.mulesoft.com is EU. CloudThinker always verifies Anypoint’s certificate and doesn’t follow redirects, so the secret is never sent anywhere else.
Required permissions
Agents can do only what the Connected App’s scopes allow, in the business groups and environments you selected.Agent capabilities
Verify the connection
Example prompts
Write access
Before any action, CloudThinker reads the app and shows its environment, version, status, and the downtime or capacity change in the approval request. If the app changes between that read and the action, the action is refused and needs a fresh read and approval. An accepted request isn’t a finished one. CloudThinker reads the app again until the deployment settles. A failed or timed-out action is never retried on its own. A restart stops the app and then starts it; if it’s interrupted, the app can stay stopped until you approve a start. Agents can’t deploy new apps, change app properties, or edit API policies. Rollback works only on CloudHub 2.0: use your release pipeline for CloudHub 1.0 and hybrid apps. Scale hybrid apps on your own servers.Troubleshooting
Anypoint rejected the Connected App credentials. Check the client ID and secret.
Anypoint rejected the Connected App credentials. Check the client ID and secret.
Anypoint rejected the token request. Use a Connected App that acts on its own behalf with the client credentials grant.
Anypoint rejected the token request. Use a Connected App that acts on its own behalf with the client credentials grant.
The Connected App lacks access. Grant reads for its Connected App record and organization, then the required Runtime Manager and API Manager scopes.
The Connected App lacks access. Grant reads for its Connected App record and organization, then the required Runtime Manager and API Manager scopes.
Connected, but agents see no apps or environments
Connected, but agents see no apps or environments
An action is refused after you approved it
An action is refused after you approved it
Security
- Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
- Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
- Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
- Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
- Set a secret expiry. A Connected App secret doesn’t expire by default. Set an expiration date, or rotate it on your normal schedule.
- Rotate after an ownership transfer. When the app’s creator leaves or loses admin rights, MuleSoft moves the app to the root organization owner. Rotate its secret, then update the connection.