Asana connector
Connect Asana to Silux Chat with a read-only connection for support tickets and cases. It is tested with a real call when you connect it and re-checked every day.
What your bot can do with Asana
Support tickets and cases
Reads the verified customer’s tickets, cases or tasks in Asana — subject, status and when each was last updated.
Customers ask: “Is there any update on my case?” · “Has my request been closed?”
Connected and tested when you connect Asana, but the bot does not answer customers from it: Asana can’t prove who is asking, and these records are personal. Email support@siluxcall.co.uk to discuss using it.
Set it up
Most businesses finish in under ten minutes. You need to be able to sign in to Asana as an administrator to create the key.
Step 1 — in Asana
- 1Asana
- 2My settings
- 3Apps
- 4Developer apps
- 5Create personal access token. Task search needs a paid (Starter or above) workspace.
Least access: grant only the read permissions named above (customers, orders, invoices, bookings or tickets — whichever this connector uses). Never use an owner or full-admin key where Asana lets you create a restricted one.
Step 2 — in Silux Chat
- 1Open Dashboard → Integrations → Connectors and search for “Asana”.
- 2Fill in:
Field Example Stored Workspace GID 12345 Setting Personal access token •••••••• Encrypted - 3Press Connect & test. The platform makes a real, read-only call to Asana with a made-up customer and shows a tick or a cross for each capability, with Asana’s exact error if something is refused.
You create an API or access token in Asana and paste it into your dashboard. It is sent as a Bearer token on every call, over HTTPS only.
How customer verification works
Asana holds no customer records that the platform can match by name and email, so this connector cannot verify customers by itself. It is tested when you connect it and re-checked every day. To plan how its data should reach your customers alongside your verification route — a connector that can look customers up, or your own Account Connect endpoints — email support@siluxcall.co.uk.
What the bot can and cannot see
Can see (after verification)
Nothing — see the verification section above.
Only these standard fields are mapped from Asana’s responses. Everything else in the response is discarded before the bot sees it.
Never sees
- passwords, security answers or login details
- records belonging to anyone other than the verified customer
- anything outside the fields listed alongside
Security
Keys encrypted at rest
Credentials are stored encrypted, shown only masked after saving, and destroyed — not just hidden — when you disconnect.
Read-only look-ups
Every capability is a look-up. The connector cannot create, change or delete anything in Asana.
HTTPS only
Calls go to the vendor’s HTTPS address, redirects are not followed, and private network addresses are refused.
Injection-safe
Values a customer types are cleaned before they are placed in Asana’s search, and URL-encoded in addresses.
Other customers filtered out
A row that names a different customer’s email is dropped, whatever the vendor’s search returned.
Checked daily
Connections are re-tested every day, and the owner is emailed if a working connection starts failing.
More: Security & data protection.
Technical details
For developers and IT teams: the Asana endpoints this connector reads, relative to https://app.asana.com/api/1.0. Values in braces come from the settings you enter.
| Capability | Request | Standard fields returned |
|---|---|---|
| Support tickets and cases | GET/workspaces/{workspace_gid}/tasks/search | id, subject, status, updated |
Test level: Documented-API tested. Each capability is run automatically against Asana’s documented example responses and must produce the standard fields; your own connection is then tested with a real call when you connect. The bot receives these through the standard Account Connect endpoints, exactly as if you had built them yourself.
Troubleshooting
| What you see | Likely cause and fix |
|---|---|
| “the vendor refused the credentials (401)” or (403) | The key was revoked, has expired or was copied incompletely, or it lacks a read permission this connector needs. Create a fresh read-only key in Asana and reconnect. |
| “That Workspace GID doesn’t look right” | Enter it in the form shown, e.g. 12345 — without https:// or a trailing slash. |
| Customers are “not matched” although they exist | Customers are looked up by email or mobile, not postcode. Check the customer’s email or mobile is saved on their Asana record, and that the surname matches. |
| A capability shows a cross but others work | That permission wasn’t granted in Asana, or your Asana plan doesn’t include that part of the API. Grant it and press Test. |
| “the vendor kept rate-limiting the request” | Asana returned “too many requests” three times in a row. The platform already waits and retries automatically (up to 10 seconds, as Asana asks); if it persists, ask Asana about your API quota. |
| Results are empty for a verified customer | The records exist under a different email or customer record in Asana, or none are recent. Check the customer’s record in Asana directly. |
Full error reference: Troubleshooting & error reference.
Frequently asked questions
Is the Asana connection read-only?
Yes. Every request Silux Chat makes to Asana is a look-up; none creates, changes or deletes anything in Asana. Give the key or sign-in read-only permissions wherever Asana offers them.
Do I need a developer to connect Asana?
No. You paste the details listed in the set-up steps in Dashboard → Integrations → Connectors and press “Connect & test”. The platform makes a real call to Asana straight away and shows exactly which features work.
How does the bot know it is really my customer?
Asana holds no customer records the platform can search, so it cannot verify customers by itself. See the verification section on this page, or email support@siluxcall.co.uk to plan the right set-up.
What happens if my Asana key is revoked or expires?
The bot tells customers it can’t check their account right now — it never pretends there are “no orders”. Connections are re-tested daily and the account owner is emailed when a working connection starts failing. Reconnect it in Dashboard → Integrations → Connectors.
How has the Asana connector been tested?
It is Documented-API tested: every capability is run automatically against Asana’s documented example responses and must produce the standard fields. When you connect, it is tested again with a real call to your own Asana account before your bot uses it.
Other productivity & no-code connectors
Airtable
Recognise and verify customers · Orders and order status
Baserow
Recognise and verify customers
ClickUp
Support tickets and cases
Google Sheets
Recognise and verify customers · Orders and order status
monday.com (boards)
Recognise and verify customers · Support tickets and cases
NocoDB
Recognise and verify customers
Notion (database)
Recognise and verify customers
Smartsheet
Recognise and verify customers
Trello
Support tickets and cases
Need help with your integration?
Our integration team can review your endpoints, help you choose the right connector and check a test run with you. Tell us which system you use and what you would like the bot to answer.