Klaviyo and Monday: AI Lead-Quality Classifier Template

Catch every new lead through a webhook, grade it hot, warm, or cold with an Agent-mode Connector node, add the profile to a Klaviyo list, and log the grade as a Monday item, all built by Miraxa from one prompt.

What It Builds

This Spojit template starts with a Webhook trigger that fires when your lead form or CRM posts a new lead. An Agent-mode Connector node reads the lead details and returns a structured grade of hot, warm, or cold using a Response Schema, so the result is always reliable JSON. From there the flow uses the Klaviyo connector to add the profile to a list, and the Monday connector to create an item that records the lead and its grade. The outcome is a triaged, list-segmented lead with a permanent record in your board.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow with a Webhook trigger that receives new leads. Add an Agent-mode Connector node that classifies the lead as hot, warm, or cold based on the company size, role, and message, and force the output to a structured schema with a "grade" field and a one-sentence "reason". Then use the Klaviyo connector to create or update the profile and add it to a list, and use the Monday connector to create an item on my leads board logging the lead name, email, grade, and reason.

Connectors Used

Webhook trigger - receives the new-lead payload as parsed JSON, verified by a signing connection.
Connector node (Agent mode) - classifies the lead and emits a structured grade via a Response Schema.
Klaviyo - create-profile (or update-profile) plus add-profiles-to-list to segment the lead.
Monday - create-item to log the lead and grade on your board.

Customize It

Change the classification rules in the prompt to match your scoring (for example, weight job title or deal value), and swap the list and board names for your own. You can add more grade buckets than three, or adjust the Klaviyo list so that only hot leads are added by routing the grade through a Condition node before the list step. The reason field is optional; drop it if you only want the grade on the Monday item.

Tips

Agent mode costs AI credits because it reasons over the lead; keep the Klaviyo and Monday calls in Direct mode so those steps stay deterministic and free of AI cost.
Define the Response Schema so grade is an enum of exactly hot, warm, and cold. That keeps downstream Condition checks and Monday status mapping predictable.
Reference upstream values with handlebars like {{ input.email }} and {{ classification.grade }} when you fine-tune the Klaviyo and Monday fields in the properties panel.

Common Pitfalls

The Webhook trigger needs a signing connection (Spojit, Shopify, GitHub, Slack, or Custom) so Spojit can verify the caller; an unsigned post will not run the workflow.
If a lead already exists in Klaviyo, prefer update-profile over create-profile to avoid duplicate work, or let the agent decide which to call.
Monday boards expect column values in a specific shape; map the grade to your real status column rather than a free-text column, or the item will save without the label you expect.