Work management · 45 pre-built actions
Asana integration with Nexus
Turn process steps into Asana work, and back again. Create and update projects and tasks from governed workflows, so the people doing the work see it where they already plan.
Pre-built actions
What you can automate
45 pre-built Asana actions, grouped by what they work on.
45
PRE-BUILT ACTIONS
- 01Projects and Tasks actions create and update work items from any workflow step.
- 02Users actions assign work to the right people.
- 03Workspaces actions organise work across teams.
Workflow
How it fits into a Nexus workflow
Asana steps run as pre-built actions. A run that uses them starts from a webhook, a schedule, a request in Nexus or another system's trigger source.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the Asana API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Approved request to project
An approved request creates an Asana project with tasks and owners, linked back to the original record.
Exception follow-up
A workflow exception becomes an Asana task for the named resolver, and the run waits for completion.
Onboarding plans
A new hire creates an onboarding project with tasks for IT, facilities and the manager.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
FAQ
Asana connector questions
- Which Asana actions are pre-built?
- Nexus includes 45 pre-built Asana actions across Users (10), Projects (15), Tasks (10) and Workspaces (10).
- Can Asana start a workflow?
- Runs that use Asana start from a webhook, a schedule or another trigger source. Asana steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the Asana API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- Jira connector
Engineering issues and projects.
- Slack connector
Messages, users and channels.
- Human-in-the-loop
Where approval belongs in a running workflow.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Asana fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.