For teams that run projects, not a service desk: each company connects its own Asana workspace, and SmartTile turns firmware advisories, VPN outages and your own Workflow rules into assigned, dated Asana tasks — commented and completed when the work is done.
Plenty of IT teams live in Asana rather than an IT Service Management (ITSM) system. For them, an alert that lands in e-mail is work nobody has assigned. ServiceAutomate connects SmartTile to your Asana — never SmartChoice's — so the things SmartTile finds become tasks with an owner and a due date in the project your team already reviews.
Any ServiceAutomate Workflow can create a task. Assignee, collaborators, project (company default, a specific one, or none), section, tags, custom fields and due in N hours are all dropdowns loaded live from your Asana. Name and notes are templates filled from the event.
A new firmware advisory opens a task in the project you route it to, with an optional assignee and section, due 14 days after detection by default (per-company override). Updates are posted as comments; after the upgrade is verified the task is commented and marked complete.
When a company routes VPN tunnel outages or admin-login events to Asana, SmartTile opens the task there alongside any other ticket system the company has connected.
In the Asana developer console: Developer Apps → Personal access tokens → New access token; copy it, it is shown once. A dedicated service account that can add tasks to the target project is simplest.
SmartTile Service Automate → Asana: paste the token, then choose the workspace and default project from the lists SmartTile reads from your account. Test confirms who you are connected as.
Pick Asana as a destination in FirmwareAutomate routing (with project, assignee, section and due-day overrides), or in VPNAutomate routing.
A Workflow's simulate shows the exact task body it would send — and warns if Asana is not connected for that company — before anything is written.
Project: IT — Network · Section: Firmware · Assignee: network engineer
Due: 14 days after the advisory was detected
Running 7.2.8 · available 7.2.10 · same-branch patch
Created by SmartTile FirmwareAutomate
/users/meTest the connection/workspaces · /projects?workspace=…Workspace and project pickers/workspaces/{ws}/users · /tags · /projects/{p}/sections · /projects/{p}/custom_field_settingsAssignee, tag, section and custom-field pickers/tasksCreate the task (project, section, assignee, followers, tags, due date)/tasks/{gid}/storiesComment on a firmware task/tasks/{gid}completed: true when the firmware work is verifiedCredentials are per company. There is deliberately no fallback to any other token — a company that has not connected gets “not connected”, never another tenant's workspace.
The personal access token is encrypted at rest and returned masked; SmartTile never logs it.
Only company admins (or your reseller) can connect, change or disconnect Asana, and only for their own company.
Every task a Workflow creates — or fails to create — is a row in the Automation Audit Ledger with the task link.
| Objection | Answer |
|---|---|
| “We are not a service desk.” | That is the point: tasks, owners and due dates in Asana — no ITSM system required. |
| “We'll get a task for every blip.” | Tasks come only from the routes and Workflows you switch on, for the events you choose. |
| “We use ServiceNow for incidents.” | Keep it. Route outages there and firmware work to Asana — routing is per company and per product. |
| “Does our wish go into our Asana?” | No. Make a Wish goes to SmartChoice's backlog; your connection is only used for your own tasks. |