Connect Asana to your WeInc site and every form entry becomes a task in an Asana project.
What it does
Every entry from every form on the site creates a new task in the project you choose. No opt-in or email address is needed.
The task is named "New <form name> entry from <name>", using the visitor's name, or their email if there is no name.
The task description lists every field the visitor filled in, followed by the site name, form name, the time it was sent and the page it came from.
Two ways to connect
Connect with Asana (easiest): sign in to Asana and approve WeInc. You don't copy any token. WeInc renews the sign-in for you in the background.
Use a key instead: paste a personal access token you create in Asana yourself. Use this if you prefer tokens, or if you don't see the Connect with Asana button.
Your Asana sign-in belongs to your WeInc account, so once you've connected, you can reuse it on your other sites without signing in again.
What you need from Asana
Personal access token (key method only): in Asana, open the developer console (click your profile photo > My settings > Apps > View developer console). Click Create new token, name it, and copy it. Asana shows it only once. Tasks are created as you, so the token's owner must have access to the project. Asana's guide: Personal access token.
Project ID (needed either way): open the project in Asana. The Project ID is the long number in the project's link, right after
/project/(or, in older links, the first long number after/0/).
What WeInc can access
With Connect with Asana, WeInc asks Asana for one permission only: create tasks (tasks:write). It uses it to create one task per form entry. Tasks are created as you, so you need access to the project.
Where to set it up
Form connections live in the builder, in the Analytics panel. Open your project, click the ··· (More panels) button in the top bar and choose Analytics. Scroll to Form submissions. Below it is a section called Send entries to.
The Analytics panel only appears in full once your site is published, so publish first. Only the project owner can add or change these connections.
Connect it
With Connect with Asana
Under Send entries to, open the Add a destination… menu and choose Asana.
Click Connect with Asana. Asana opens and asks you to approve WeInc. Approve it.
You come back to the builder. If the form has closed, choose Asana in Add a destination… again. It now says Connected to <your Asana name>.
Paste the Project ID.
Click Save. The connection appears in the list with the On box ticked.
With a personal access token
Under Send entries to, open the Add a destination… menu and choose Asana. If you see a Connect with Asana button, click Use a key instead.
Paste the Personal access token and Project ID.
Click Save. The connection appears in the list with the On box ticked.
To switch back from the key fields, click Connect with Asana instead.
Test it
Click Test next to the connection. WeInc sends a sample entry, and when it works you see Test entry sent. and a task called "New Contact entry from Test Person" appears in your project. Delete it afterwards.
If something goes wrong
Each saved connection has a dot next to its name: blue means the last send worked, red means it failed, grey means it is paused. The last error is shown under the name.
"<field> is required" or "<field> doesn't look right" when saving: a value is missing or not in the expected format. Copy it again, with no extra spaces or characters.
"Asana is no longer connected. Reconnect it in the forms panel.": you used Connect with Asana and WeInc can no longer sign in to Asana for you (for example, access was removed in Asana). Remove the connection, choose Asana again and click Connect with Asana.
"Access refused (401)" or "(403)": Asana did not accept the personal access token or sign-in. With a token, create a new one and add the connection again. With Connect with Asana, WeInc renews the sign-in and tries once more by itself; if it is still refused, connect again.
"Paused: the key was refused three times." If real form entries are refused three times in a row, WeInc pauses the connection so it stops failing. Test sends do not count toward this. Click the bin icon to remove it, then add it again with a new personal access token, or by clicking Connect with Asana.
Other errors (for example "Error 404" or "Error 422"): usually a wrong Project ID. Check it in Asana, then remove and re-add the connection.
WeInc tries each send twice (one retry after a short pause) and waits up to 8 seconds for Asana to answer. The entry is always kept in Form submissions either way, so nothing is lost if a send fails.
Saved keys can't be viewed or edited later. To change a value, remove the connection and add it again.
Pause or disconnect
Pause: untick the On box next to the connection. It shows Paused and nothing is sent until you tick it again.
Disconnect: click the bin icon (Remove). WeInc deletes the saved key. Anything already in Asana stays there.
To fully revoke access, also delete the personal access token in Asana, or, if you used Connect with Asana, remove WeInc from your authorized apps in Asana (profile photo > My settings > Apps). Any connection still using it will then fail and pause after three refused entries.
Need help? Message us from the chat bubble in the corner of WeInc.