Connectors

Connectors let the agent reach external tools to pull in assets. The canonical one is Figma — point the agent at a frame and it imports the artwork directly.

Setting up a connector

Connectors are account-level — set one up once and every project you own can use it.

Tokens are encrypted at rest on the umicat backend. They never reach your game, your game's code, or the agent — every fetch is brokered through the platform, which holds the credential and hands back only the bytes.

Disconnecting

Settings → Connectors → the connector → Disconnect, and confirm. The stored token is deleted.

You can reconnect later without losing imported assets — they're already in your game's asset library.

Figma

What's supported:

• Frame export. Tell the agent the Figma URL of a frame and the layer name; the agent uses Figma's REST API to render it to PNG at 1× / 2× / 3× / 4× and saves it as an asset in your game.
• Style consistency. Once you've imported one frame, asking for more frames from the same file produces visually consistent assets — same style anchor as AI generation.
• Auto-naming. Asset filenames default to the Figma layer name, sanitised.

Asking the agent:

I have a Figma file with the player character at this URL:
https://www.figma.com/file/abc123/MyGame?node-id=12-34

Import the "Player Idle" frame as the player sprite, at 2x.

The agent:

1. Looks up the file via your connected Figma PAT.
2. Finds the layer matching the layer name (uses the node-id from the URL fragment when present).
3. Exports it as PNG.
4. Saves it as an asset and uses it for the player entity.

Getting a Figma PAT

Open Figma → click your avatar → Settings → Personal access tokens → Generate new token. Give it a name like "umicat", choose Read scope (write is not needed), copy the value, paste it into Settings → Connectors.

The PAT can be revoked any time from the same Figma settings page.

Limits

• One connection per provider per umicat account.
• Figma rate-limits are pass-through — if you hit them, you'll see a toast and can retry.
• Files must be visible to your Figma account (org-private files require an org-member PAT).

Coming soon

• Google Drive — import images / audio from Drive folders.
• Dropbox — same shape.
• Sketch / Affinity — under consideration.

If you want a specific connector, file a support ticket from Settings → Help & Support and we'll prioritize based on demand.

Why not "just upload"?

You can always upload directly via Assets Manager → + Add → Upload. Connectors are for when:

• The source of truth is in the external tool (you redesign in Figma constantly and want imports to track).
• You want consistency between dev iterations of the same asset.
• You don't want to manually export from another app every time.

Direct upload is simpler if you're not iterating on the asset itself.

Security model

• PATs are AES-GCM encrypted at rest.
• Decrypted only inside the platform backend when it fetches on your behalf — never in the agent, your game code, or chat history.
• A revoked PAT (revoked at the source service) stops working immediately for all umicat calls.

Next steps