CloudFiler
Connect Cosmo to CloudFiler to list and create project filing locations from chat.
The CloudFiler integration lets Cosmo list the project filing locations in your CloudFiler tenant and create new ones — for example when a new job or project starts.
What it can and cannot do
CloudFiler's public API is deliberately narrow, and Cosmo can only do what it allows.
| Can do | Cannot do |
|---|---|
| List your filing locations, optionally filtered by name | Read, search or export the emails filed in a location |
| Create a new filing location | Import emails or email folders |
If you ask Cosmo to find an email in CloudFiler, it will tell you that the API does not expose filed email. CloudFiler has said email access is on its roadmap; this integration will gain it when the API does.
Before you connect
CloudFiler does not use a sign-in window. Its API is available to enterprise customers, and uses an API token that your CloudFiler contact generates and activates for your organization.
| Item | Used for |
|---|---|
| API token | Connecting |
The token works as a service account: it does not depend on any one person's permissions. Treat it like a password and do not share it in tickets or chat.
CloudFiler has no sandbox. Anything Cosmo creates is created in your live tenant.
Connecting
- Open Cosmo Desktop → Customize → Integrations.
- Find CloudFiler under "Add new integration" and click Connect.
- Enter a label (for example
Work) and paste your API token. - Cosmo checks the token with CloudFiler before saving it, using a read-only request. A token CloudFiler refuses is rejected on the spot, with nothing stored.
The token is stored with your connection on the Cosmo server, and Cosmo only sends it to CloudFiler's API host (api.cloudfiler.io).
Creating locations
New locations use your tenant's default location permissions, so they are available to the relevant users straight away. Cosmo checks the existing list first so it does not create a duplicate, and asks you to confirm before creating anything.
Example requests:
- "List the CloudFiler locations that contain Harbour."
- "Create a CloudFiler location called Harbour Tower Phase 2."
Troubleshooting
- "CloudFiler rejected that API token" — the token was copied incompletely, has not been activated yet, or has been deactivated. Ask your CloudFiler contact to activate or reissue it.
- Connected, but no locations appear — the API returns the locations visible to the token's tenant. Check with CloudFiler that the token is provisioned for the right tenant.