Hi @Theleary 

Good question.

Please post screenshots with how your Zap steps are configured in order for us to have proper context, thanks.

@Theleary 

Are you able to provide screenshots of your Zap action step for Asana?

I think this is what you need . I meant to send this.  I sent half of output,  I think the first part is what you might need. If not, Ill post the rest. Thank you so much!  I have spent too much time trying to figure out something that seems pretty simple. 

@Theleary 

It’s still unclear which Zap action step you are using and how that Zap step is configured with variables mapped from the trigger step.

Can you post more screenshots showing that?

Sorry Troy, I thought I added those previously.  see below. 

@Theleary 

Are you getting an error when testing the Asana Create Task step?

Else, please clarify what you mean by “sending a message and not creating a Task”.

I do not get any errors when testing the task.  When it runs the Zap, it sends the data into Asana as a message and is not creating a Task.  See below.  I have tinkered with this for a while. 

@Theleary 

The Zap is configured to create an Asana Task.

Perhaps you have other apps connected to Asana that are creating the Message or other Asana Rules configured that are causing the message.

You can check your Zap Runs to see the DATA IN/OUT for each Zap step: https://zapier.com/app/history/

The DATA OUT for the Asana Create Task step will include the Asana Task ID that was created.

Hey @Theleary! Just wanted to follow up here and see if you were able to figure out the issue with your zap sending a message and not creating a task? It looks like everything is set up correctly, I’m curious to see if you were able to find a solution