Asana
What comes back gets scheduled instead of only read. Turn a critical answer into a task, collect feature requests in their own project, and start a survey once the milestone ships.
Workflows you can build with it
Each example is a workflow you can set up with an automation service, an AI assistant or your own application.
Follow-up becomes a task
A critical response creates a task in the responsible project with an assignee and a deadline. For teams where otherwise nobody is formally responsible.
Feature requests in their own project
Responses categorised as a feature request become tasks in the project you prioritise from, ready for the next round. For product owners who want one source instead of five channels.
Ask once the milestone ships
Completing the milestone task publishes the prepared project survey and files the link as a task. For project leads who would otherwise skip the retrospective.
Comment on the task it concerns
When a response refers to a task that already exists, the workflow adds the verbatim as a comment. For teams who want one thread per thing.
What the integration transfers
Each point is a separate example in the direction of the arrow. Configure each workflow independently and link the relevant survey for actions on an existing survey.
empirio.ai → Asana
- A task in the responsible project, with an assignee and a due date
- The open answer as a comment on a task that already exists
- Custom fields for score, segment and survey
Asana → empirio.ai
- New project created: duplicate a prepared survey for it
- Task in the “Approval” section completed: publish the survey it is linked to
- Milestone task due date moved: move the survey’s run window with it
How to set it up
Custom fields belong to the project rather than to a single task, so anything not defined there is dropped on write. Select fields only accept options that already exist, and an assignee has to be a member of the workspace.
