Auto-triage Webflow contact form submissions

Classify every Webflow contact form submission, file support tickets in Linear, ping the right Slack channel, and quietly drop recruiter spam.

Agentic Task
WebflowLinearSlack BotOperationsCustomer SupportFeedback TriageLead EnrichmentNotifications & Alerts

Build an agent workflow that triages every new submission from my Webflow contact form and routes it to the right place without a human triaging first.

Trigger: a webhook from Webflow on the form_submission event, scoped to my contact form (filter by form name so other forms on the site are ignored).

On each submission, the agent should read the message body plus any subject, category, or topic field on the form and classify it into exactly one of: support_issue, sales_lead, recruiter_or_spam, partnership, or other.

Routing rules by category:

- support_issue: call Linear Create Issue in the support team. Write a clean one-line title that summarizes the actual problem (not the raw form text). Put the customer's email and the full original message in the description. Infer a priority from urgency cues in the message (Urgent for outage / can't access / paying-customer-impacting language, High for blocking-but-not-down language, Normal otherwise). Then call Slack Send a Message to the support channel with a short summary and a link to the new Linear issue.

- sales_lead: call Slack Send a Message to the sales channel. Include a one-line qualification summary (company, role if available, what they're asking for, any size or timing signals) plus the contact name and email.

- partnership: call Slack Send a Message to the partnerships channel with a one-line summary of who they are and what they're proposing, plus contact details.

- recruiter_or_spam: log silently and stop. Do not notify any channel.

- other: post to the partnerships channel as a fallback with a note that it didn't fit a category, so a human can decide.

Use the Slack Bot integration for all Slack messages (not the user OAuth one), so posts are attributed to the bot and don't depend on any one person's account.

The classifying, the priority decision, and the qualification summary are the judgement calls that make this an agent rather than a static workflow. Keep the agent's instructions explicit about category definitions and priority cues so behavior is consistent across submissions.

Additional information

What does this prompt do?
  • Reads every new Webflow contact form submission the moment it lands.
  • Decides whether it's a support issue, sales lead, partnership pitch, recruiter spam, or something else.
  • Files support issues straight into your Linear support team with a clean title, the customer's email, and a priority guess based on urgency cues.
  • Posts sales leads and partnership pitches into the matching Slack channels with a one-line summary and contact details.
  • Silently drops recruiter spam so your inbox stays quiet.
What do I need to use this?
  • A Webflow site with a contact form and access to add a webhook.
  • A Linear workspace and the support team you want issues filed into.
  • A Slack workspace with channels for support, sales, and partnerships.
  • A rough idea of the urgency cues your customers use, so priority guesses match how your team already triages.
How can I customize it?
  • Add or rename categories. If you also get press inquiries or investor outreach, give them their own Slack channel.
  • Tune the priority rules. Tell the agent which words on your form mean urgent versus normal.
  • Change the Slack channels and the Linear team. Point each route at whichever inbox owns that kind of work today.
  • Scope to specific forms. If your site has more than one form, restrict the workflow to just the contact form.

Frequently asked questions

Does this work with any Webflow contact form?
Yes. As long as the form is on a Webflow site you control, the workflow can listen for new submissions. If you have several forms, you can scope it to a specific one by name.
What if a submission doesn't clearly fit any category?
The agent has a catch-all category for ambiguous submissions. You can choose to route those to a general inbox channel or have them filed as low-priority tickets for human review.
How does it decide priority on support tickets?
It reads the message for urgency cues like outage language, mentions of paying customers, or phrases like 'broken' and 'can't access'. You can tune the rules in plain English.
Can I change the channels or the Linear team later?
Yes. Every destination is editable. Swap a Slack channel, switch to a different Linear team, or add a new category whenever your routing needs change.
Will recruiter or partnership spam still clutter my inbox?
Recruiter spam is logged and dropped without a notification. Real partnership pitches still post to the partnerships channel so a human can look.

Stop manually sorting your Webflow contact form.

Connect Webflow, Linear, and Slack once, and every new submission lands in front of the right person automatically.