Project management · via Zapier

Connect Zunoform to Asana via Zapier

This is not a one-click native integration. Zunoform posts every completed response to a Zapier catch hook, and your Zap does the rest — so there is no Asana button inside Zunoform and no OAuth connection between the two products. What you get instead is a webhook connection with field mapping you control in Zapier.

Turns each submission into an Asana task in the project you choose, with the form's answers in the task description and a due date if you collect one.

Start free — no card See native integrations

The Zapier integration is on Zunoform’s free plan — 500 responses a month, no card. Webhooks by Zapier requires a paid Zapier plan; destination account requirements and task limits also apply.

Example workflow

Give creative requests a usable task brief

A creative intake form can collect a deliverable, audience, deadline and context, then create an Asana task for triage. The requested deadline is a preference until your team accepts it; make that distinction clear in the form's ending message.

Prepare your Asana account

Choose the project and a default owner for incoming work. Start with a task title and description, then add structured fields only when they are exposed by the action and useful to the team.

Four steps, start to finish

Start with a published Zunoform form, a Zapier plan that includes webhooks, and access to the destination account. Some destinations require additional permissions or setup.

Create a Zap with a Catch Hook trigger

In Zapier, create a new Zap and choose Webhooks by Zapier as the trigger app, then Catch Hook as the event. Zapier generates a URL for you and shows it on the next screen. Copy it.

Paste the URL on the Zapier card in Zunoform

Open your form in the Zunoform builder, go to the Integrations tab, and paste the URL on the Zapier card. We only accept an https address on zapier.com, so a typo is rejected rather than silently failing later.

Submit a test response so Zapier learns the shape

Publish the form and fill it in once yourself. Zapier's trigger step will pick that submission up as sample data — without it, the field list in the next step is empty and there is nothing to map.

Map your fields to Asana

Add an action step and choose Asana. Connect your account, then pick the action that creates a task in a project. Zapier's action list changes over time, so choose from what it shows you rather than hunting for an exact name. Drag your form's answers into the fields, test the Zap, and turn it on.

Suggested field mapping

Use this example to plan your form. Select the actual fields from your captured test response and the action available in your account; these are mapping suggestions, not a preconfigured Zap.

Deliverable and project name: Destination: Task name; Example: Landing page illustrations — autumn launch.
Audience, goal and references: Destination: Task description; Label each answer so an assignee can scan the brief.
Requested deadline: Destination: Due date or description; Keep it in the description if the date is not yet committed.
Fixed reviewer: Destination: Assignee; Select an actual project member; a respondent's name is not an Asana user ID.

What Zapier receives

The payload includes formId, formName, responseId, submittedAt, status, answers and metadata. Answers are keyed by field ID, not by question label; inspect a test response to identify the answer you want. Multi-part answers can contain nested values, and uploads contain file references rather than binary attachments. Replacing a question can change its ID, so retest mappings after editing the form.

Delivery uses a background queue with retries for failed webhook requests. A successful hook does not confirm the later Asana action succeeded. Check Zap history, and use responseId in a lookup or a processed-response log when duplicate processing would matter. Earlier responses are not automatically replayed when you connect the hook.

Test before sharing your form

Open the created task as the person who will do the work. Confirm they can see the project and references, and that the deadline has not shifted because of date formatting.

If the result is missing or wrong

When the task exists but is hard to find, check its project membership and assignee. A successful create action does not prove it landed in the team's working view.

Check the current Asana actions in Zapier and Zapier’s webhook setup and plan requirements before configuring your account. Action availability and permissions depend on your connected account.

Questions people ask

Can the Zap assign the task to someone?

Yes. Set a fixed assignee in the Zapier action, or map an answer to the assignee field if your form asks who should handle the request. Round-robin assignment needs a Zapier paths step or a third-party tool.

Should I use Asana or a native integration for intake forms?

If Asana is where the work happens, this Zap is the right shape. If you only need the team to see submissions, our native Slack integration on Pro is one fewer moving part and does not consume Zapier tasks.

Is this a native Zunoform integration?

No. Zunoform sends each completed response to your Zapier catch hook; you configure the destination and field mapping in Zapier. The Zunoform connection is included on Free, but Webhooks by Zapier requires a paid Zapier plan. Native options include Google Sheets and Zoho CRM on Free, with Slack, Notion, HubSpot, Mailchimp, Airtable and Excel on Pro. Form notification emails on Free require your own SMTP configuration; platform-sent form emails require Pro or Business.