title:	In, Val, Out
description:	Manage input (like user signups) and automate output (e.g., Slack messages)

A common pattern in Val Town is what we call In, Val, Out, or Input/Val/Output (I/V/O). You have data coming in, and you want to do something with it then output something. For example:

Webhook received from Supabase when a user signs up
Enrich the user data with Clay
Send your team a Slack notification

There's a combinatorial explosion of possibilities, so we've listed some examples and ideas. Feel free to add new use cases, or ask us to lend a hand—we're happy to help.

Input

Messages, email:

Events:

You can hook up any tool in your stack as long as it can send data to your val's HTTP endpoint or email. That might be data from Clerk, Vercel, Linear, Sentry, Cal.com, Shopify, PostHog, Cloudflare, Google Forms, Typeform, or anywhere else—just send it to a val.

Val

AI enrichment, browser automation:

You can also call your LLM of choice, like Claude, or run arbitrary enrichment and analysis using other tools, like Exa.

Output

Notifications:

Whether you use Resend, Loops, Twilio, or some other platform, as long as it has an API you can use it in Val Town.

Persistence:

You can of course store your data in Cloudflare R2, Notion, or any other database or CRM. Let us know if you'd like help with your use case, and we'll continue to add examples to this docs page.