Turn Typeform creative briefs into well-formed Wrike tasks

Every new design intake form becomes a clean Wrike task with a derived title, due date, deliverables, and assignee, plus a Slack ping for the design team.

Agentic Task
TypeformWrikeSlackMarketingOperationsFeedback TriageDocument ProcessingNotifications & Alerts

Build me an agent workflow that turns new Typeform creative brief submissions into well-formed Wrike tasks for our design team.

Trigger: a Typeform webhook firing on each new response to our Creative Brief form. On every fire, take the response ID from the webhook payload and call Typeform Retrieve Responses to pull the full answer set for just that response.

Then have the agent read the brief end-to-end and derive a structured spec from it: a short, clean task title (not the form name plus a timestamp), a target due date based on what the requester asked for (default to two weeks out if no date is given), a deliverable list with assets, sizes, and channels, the target audience, and a priority signal (low / medium / high) based on language like 'launching Monday' or 'campaign in flight'. Also extract any clarifying questions the agent needs answered before the designer can start, things like missing copy, unclear brand, no reference, no measurable goal.

Pick an assignee from the design team. Call Wrike List Contacts to fetch the team. By default, rotate assignments across the design team. If the brief contains a workstream tag (for example 'paid social', 'web', 'brand'), prefer the designer who owns that workstream. Fall back to a configurable default lead if no one matches.

Then call Wrike Create Task to file the brief into our Creative Requests folder. The task title is the derived clean title. The description is a structured rewrite of the raw form answers in this shape: a one-paragraph summary at the top, then sections for Deliverables, Audience, Priority, Source brief (a quoted excerpt of the requester's own words so nothing is lost), and Requester (name and email from the form). Set the due date from the derived target due date. Set the assignee from the contact we picked.

If the agent extracted any clarifying questions, follow up with Wrike Create Task Comment on the new task, listing the questions as a numbered list and tagging the requester so they see it in the task thread.

Finally, post a card to the design Slack channel via Slack Send a Message. The message is a one-sentence summary of the request (who, what, when), a link to the new Wrike task, and a 'Needs clarification' tag if there are open questions. Use Slack mrkdwn formatting.

Configurable inputs the user should set up front: Typeform form ID, Wrike Creative Requests folder ID, Wrike design team contact IDs (and an optional workstream-tag map), default lead, default due-date offset, and the Slack channel ID for the design team.

Goal: turn messy intake forms into Wrike tasks the design team can actually start on, with the AI doing the cleanup, routing, and gap-spotting that a plain form-to-task Zap can't do.

Additional information

What does this prompt do?
  • Watches your Typeform creative brief and fires the moment a new request comes in.
  • Reads the raw answers and rewrites them into a clean Wrike task with a real title, due date, deliverables list, target audience, and priority.
  • Picks a designer to own the work and routes the task into your Creative Requests folder so nothing sits in a form inbox.
  • Posts any clarifying questions back on the task itself, then drops a one-line summary into your design Slack channel with a link to the new task.
What do I need to use this?
  • A Typeform account where your creative brief lives.
  • A Wrike workspace with a Creative Requests folder and your design team added as contacts.
  • A Slack workspace and the channel where your design team gets new-request pings.
How can I customize it?
  • Change which Wrike folder the new task lands in, or route different request types to different folders.
  • Adjust how the designer is picked: rotate through the team, match by workstream tag from the form, or always send to a lead.
  • Tweak the Slack channel, the summary tone, and whether clarifying questions are required before a designer picks it up.

Frequently asked questions

What does the AI actually add on top of a plain form-to-task setup?
It rewrites messy free-text answers into a structured brief, derives a sensible task title and due date, calls out missing information as clarifying questions, and chooses a designer instead of dumping everything on one person. You start the day with tasks that are ready to work, not raw form dumps.
How does it pick which designer gets the task?
It looks up your design team in Wrike and either rotates assignments or matches the request to a person by workstream, skill tag, or whatever signal you tell it to use. You can change the logic in plain English.
What if the brief is missing important details?
The agent still creates the task so it does not get lost, then posts a comment on the task listing the questions the requester needs to answer before work can start. The Slack message flags it as needing clarification.
Does this replace our Typeform-to-Wrike Zapier connection?
Yes. The difference is the AI cleanup step in the middle. Zapier hands raw form answers to Wrike. This workflow hands Wrike a usable brief with a real title, due date, deliverables, and an owner.
Can I use this for other intake forms, not just creative briefs?
Yes. Point it at any Typeform you use for intake, change the target Wrike folder, and adjust the fields the agent extracts. The same pattern works for legal, IT, ops, or RevOps intake.

Stop turning creative briefs into a copy-paste tax.

Connect Typeform, Wrike, and Slack once, and every new brief lands as a ready-to-work task with an owner.