Skip to main content
Book a demo

Connect Asana to ECA

Give ECA governed access to Asana’s 39 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo ECA setup guide

Set up

Add Asana to ECA in four steps

Admins approve the server once. Everyone in ECA then gets it through the same governed connection.

  1. 1

    Approve Asana in Runlayer

    Add Asana from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect ECA to Runlayer

    Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches Asana’s 39 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    ECA setup guide
  3. 3

    Sign in to Asana

    Each user signs in to Asana with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Asana from ECA

    Asana’s approved tools appear in ECA. Every call is checked against policy and recorded.

Tools

39 Asana tools in ECA

Runlayer policy decides which of these ECA users can call.

  • Add comment

    Add a comment to a task.

  • Create project

    Create a new project with optional sections and tasks in a single operation.

  • Create project confirm

    DEPRECATED; DO NOT USE.

  • Create project confirm populate

    DEPRECATED; DO NOT USE.

  • Create project from template

    Create a project from a project template.

  • Create project preview v3

    Show a visual preview of a project structure before the project is created in Asana.

  • Create project status update

    Post a status update to a project or portfolio.

  • Create task confirm

    DEPRECATED; DO NOT USE.

See all 39 Asana tools

Control

What Runlayer can see and stop in ECA

Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.

  • Gateway policy (available)

    Every Asana call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination