Workspace Resources
Flows are what you build. Resources are what flows are built from — the connections, tools, values, and keys that live in the workspace rather than inside any single flow.
Keeping them outside flows is the point. Change a credential once and every flow using it picks up the change; store a phone number as a variable and you update it in one place instead of eleven.
What's here
| Resource | What it holds | Where it's used |
|---|---|---|
| Credentials | Connected accounts and API keys for outside services — Instagram, WhatsApp, Zoho, AI providers, and around a hundred more | Triggers, tools, and thinking nodes |
| Tools | Custom tools you define, on top of the built-in catalogue | Tool and Agent nodes |
| Templates | Ready-made flows you can copy, and your own flows saved for reuse | Starting a new flow |
| Variables | Workspace-wide values — a support email, an API base URL, a company name | Anywhere {{ }} works |
| API keys | Keys that let your own code call Flowera | The prediction API and the MCP server |
Everything is workspace-scoped
A resource belongs to exactly one workspace. Switch workspaces and you get a different set of credentials, tools, variables, and keys — there is no sharing and no leaking between them.
That's usually what you want: a client's Instagram account has no business being visible in another client's workspace. It also means that if a list looks empty, the first thing to check is which workspace you're in.
Who can change what
| Role | Can view | Can create / edit / delete |
|---|---|---|
| Owner | Everything | Everything, plus workspace settings and members |
| Editor | Everything | Everything except workspace settings |
| Viewer | Everything | Nothing |
See Roles & permissions.
Viewing a credential never reveals its secret. Flowera stores secrets encrypted and shows only the name and dates — even to owners. To change a secret you replace it, you don't read it.
In this section
- Credentials — connect accounts and providers
- Tools — build a tool your agents can call
- Templates — start from something that already works
- API keys — call Flowera from your own code