Asana integration
Asana is on the map, not in the product yet.
Content review tasks created in the Asana project your team already runs, with due dates that keep drafts moving.
How it works
Asana connects through OAuth, or a personal access token if you prefer, against the standard API at app.asana.com. When the pipeline produces work for a person, chiefly a draft ready for review, we create a task in the project you chose, with a due date, a description carrying the context, and a link back to the item in SearchHandled. Review queues live where your team already plans its week instead of in a dashboard someone has to remember.
In the loop, Asana carries the human checkpoint in the write step. A draft is only as good as the review it gets, and reviews happen when they appear as tasks with dates in the tool the team actually opens. Completing the task in Asana closes the checkpoint, and the piece moves on to publish. For agencies, OAuth is the right connection method, since personal access tokens are bound to the person who made them and retire when that person does.
Best forTeams and agencies who plan work in Asana and want the content review queue managed as real tasks with due dates.
Setup, step by step
- Click Connect on the Asana card and choose OAuth, or paste a personal access token if you prefer.
- Approve the authorization in Asana if connecting through OAuth.
- Pick the project where review tasks should be created, and optionally a section within it.
- Set the default due-date offset for review tasks, such as three days after the draft is ready.
- Create the test task and confirm it appears in the project with the due date and link.
Best practices
Agencies should connect with OAuth
A personal access token belongs to the person who created it and dies with their account. OAuth connections survive staff changes gracefully, which matters when the connection outlives any one employee.
Give reviews a real due date
The due-date offset you configure is what keeps drafts from aging in the queue. Pick a number your team can honor, because a due date that is routinely ignored teaches Asana to be ignored too.
Use a section for the pipeline
Routing tasks into a dedicated section, such as Content review, keeps pipeline work visible without tangling it into unrelated project lists, and Asana's rules can assign from there automatically.
Complete the task to close the loop
Marking the task complete is the signal the review checkpoint is done. Approve the draft in SearchHandled through the task's link, then complete the task, and the piece proceeds to publish.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
Personal access tokens are user-bound
A PAT authenticates as the individual who created it, so when that person leaves and their account is deactivated, the connection dies with them, often unnoticed until tasks stop appearing.
How we handle itWe recommend OAuth at setup, especially for agencies, and flag PAT-based connections in your dashboard so the dependency on one person's account is visible before it becomes an outage.
developers.asana.com
Project access follows the connecting user
Tasks can only be created in projects the connected account can access, so a permissions change or a project moved to a private team breaks creation even while the connection looks healthy.
How we handle itTask creation failures surface immediately in your dashboard with the project named, and re-selecting a project or restoring access fixes it without reconnecting from scratch.
developers.asana.com
Questions teams ask
- Should we use OAuth or a personal access token?
OAuth for almost everyone, and definitely for agencies. A PAT is bound to one person's account and stops working when they leave. OAuth keeps the connection independent of any single employee's tenure.
- What tasks does SearchHandled create?
Review tasks for drafts awaiting a human pass, with a due date, context in the description, and a link to the draft in SearchHandled. Routine pipeline events go to notifications, not your project.
- Can SearchHandled see or change our other Asana tasks?
We create tasks in the project you selected and read back the status of those tasks. Your other projects, tasks, and conversations are not read or touched.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Asana matters moves it up the rollout.