Connectors
Let fluos read briefs and brand assets straight from your tools.
Connectors give the agent read access to the tools where your source material already lives, so you can point at a Figma frame or a Notion doc instead of exporting and re-uploading it.
Open Skills and Connectors in the sidebar and switch to the Connectors tab.
Available connectors
| Connector | What fluos can use it for |
|---|---|
| Figma | Read frames, components, and design tokens for brand-accurate layouts |
| Notion | Pull briefs, scripts, and campaign docs |
| Google Drive | Read docs, sheets, and files you point it at |
| Slack | Read the thread where a request was discussed |
| Linear | Read issues and projects for release and changelog videos |
Connecting
Press Connect on a connector and complete the OAuth flow in the popup. There are no API keys to paste and fluos never sees your password — authorization is handled by the provider and fluos only receives a scoped token.
Once connected, a toggle appears. A connector only affects builds while its toggle is on, so you can stay connected but keep it out of the agent's context until you need it.
Using one
Just refer to the source in plain language once the connector is enabled:
Use the "Q3 Launch" brief in Notion as the script for a 30-second explainer.Match the type scale and colors from our Figma design system file.Scope and privacy
- Connections are workspace-scoped. Connecting Figma in one workspace does not connect it in another.
- Connectors are read-only — fluos never writes back to your tools.
- Disconnecting revokes fluos's access immediately.
If Connect does nothing
Connectors depend on server configuration. If the Connect button is unavailable or the popup closes without completing, connectors are not configured on your deployment — everything else in fluos works normally, and you can upload the same material to the Library instead.