To use an agent with Utin, create a personal access token and store it in the agent’s secure key storage.
What you’ll achieve
You’ll have a connected agent that can list the companies, workspaces and accounts available to it.
Before you start
You need a Utin account and an agent that can store an API key securely outside the conversation.
1. Connect your accounts in Utin
Open Add Connections and connect the social or advertising accounts you want to use. Complete the Facebook, Instagram, Google or TikTok sign-in in Utin.
2. Limit access
A Utin token has the same access as the person who creates it. Use a team member whose permissions fit the work you want the agent to do. For example, reporting does not require access to publishing or messages.
3. Create the token
Open Account → View profile → Personal access tokens and select Create token.
Copy the token into the agent’s secure key storage. Do not paste it into a normal chat, email or shared document. You can revoke the token in Utin at any time.
4. List what the agent can access
Run one instruction and let the agent return the companies, workspaces and connected accounts available to it.
Prompt to copy
List the companies, workspaces and connected accounts available to you in Utin.
5. Choose where to work
Choose a company and workspace from the list, then use that workspace name in your next instruction. If something you expected is missing, check the account under Add Connections in Utin.
Good to know
The token only gives access to what its owner can already see and do in Utin. Social and advertising accounts are connected or reconnected from the Utin interface.
If something does not work
- Not authorized: create a new token and replace the one in the agent’s secure key storage.
- A workspace is missing: check that the token owner can access it in Utin.
- An account is missing: check its status under Add Connections, then ask the agent to refresh the list.
What to read next
Next, learn how to publish posts with an agent . Developers can use the Utin API companion for endpoint details.