Connect Asana

What is this connection for?

Asana allows ELChat to find tasks, create, update, complete and add comments.

What you need

Identifier	Role	Mandatory
Personal access token	ELChat authorization with the rights of your Asana user	Yes
Workspace ID (workspace_gid)	Define the space to search for	Yes
Project ID (project_gid)	Set the default project to list and create tasks	Mandatory in current form

A personal token acts with the same rights as its owner and remains valid until its revocation. Asana recommends it for personal or internal use; a multi-user application should normally use OAuth. See the Official Documentation of Personal Tokens Asana.

Step 1 — Create the token

1. Connect to Asana with the user who can access the project.
2. Open Asana Developer Console.
3. Select Personal access tokens.
4. Create a new token namedELChat.
5. Copy the token immediately and keep it in a safe place.

Step 2 — Find IDs

• A project is the number in the URL when you open this project:https://app.asana.com/0/PROJECT_GID/....
• The GID workspace is the digital identifier of the space to which the project belongs.

Information to be completed: Asana does not always display the GID workspace directly in the standard interface. If you don’t know him, ask the Asana administrator or retrieve him via the official API explorer with the token. Do not copy the ID of a task instead.

Step 3 — Connect Asana to ELChat

1. Open Dashboard > your site > IA Actions > Connectors.
2. Click Connect on the Asana map.
3. Paste the personal token.
4. Inform the ID of workspace.
5. Inform the default project ID if you want to list and create tasks in this project.
6. Validate.

Check connection

Ask ELChat to list the configured project tasks or search for a known test task. Compare the name, expiry and status in Asana.

Capacity available

Actual capacity	Type
List default project tasks	Reading
Find a task in the workspace	Reading
Create Task	Writing
Edit Task	Writing
Mark a task as completed	Writing
Leave a comment	Writing

The engine can technically operate without a project for some searches, but the current form requires this ID. Without a default project, the list and creation in this project fail. Without workspace, global search fails.

Reconnect, Disconnect and Troubleshoot

To replace the token, create a new one, reconnect and test before revoking the old one in the developer Console. Disable stops ELChat, but only Asana revocation actually invalidates the token.

• **Project not configured:**inform theproject_gidcorrect.
• **Workspace not configured:**inform theworkspace_gidspace containing the project.
• Unobtainable task: verify that the token user has access to the project and that the task is not in another workspace.
• Access denied: correct the rights of Asana member; the token does not bypass user permissions.

Security and limitations

Use a dedicated account if possible. The connector does not handle portfolios, objectives, forms, rules or attachments. The Asana API limits apply.

Example: Configuring a Support Project

For a projectSupport clients — France, provide:

• ** personal token:** the secret value created for the support user;
• workspace GID:120000000000001 ;
• GID project:120000000000101.

The workspace defines the searchspace and the project is the default destination for lists and creations. First ask for the project tasks and compare a test task; only create a task after confirming that these two IDs belong to the same perimeter.