Turn a promise into a task
The proposed flow would let an authorized agent create a selected follow-up with the support reference attached.
Integrations Asana
AsanaPlanned
AsanaPlannedAsana follow-ups that keep the support context.
Plan an Asana connection for deliberate customer follow-up tasks, with conversation references and clear assignment boundaries.
Planned connector. Native setup is not available yet. The workflows below describe the intended scope; release depends on provider access and testing.
Team projects
What we’re planning to connect.
- 01Asana
- 02Planned connection
- 03Message support
Assign the responsible person
Project membership and task ownership need explicit mapping before a request is handed off.
Close the communication loop
Task completion should prompt a reviewed support update; it should not automatically expose internal comments to customers.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Selected project
Assigned teammate
Minimal task summary and conversation link
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Pick one support follow-up project and decide which task fields may leave Message.
- 02
Agree on data and permissions
Decide which fields may be read, which people may use them and whether any separate write action is needed. Native setup is not available yet.
- 03
Define the acceptance test
Test a teammate without project access and a repeated event to prevent duplicate or inaccessible tasks.
Before you connect
Asana integration questions
Can I connect Asana to Message today?
The native connector is planned. The workflows on this page describe the proposed design; there is no native installation to activate yet.
What should we test before using it with customers?
Test a teammate without project access and a repeated event to prevent duplicate or inaccessible tasks.