Posts in Integrations · Search all posts
Slack doesn't fly at the enterprise. Teams is the stack. The webhook story changed in 2025 — here's the current working path for posting form submissions to a Teams channel from Laravel.
Newsletter form fills. Email lands in Laravel. Mailchimp's audience stays empty until someone exports manually. A queued listener + the Lists API closes the gap — with the double-opt-in note that keeps EU lawyers happy.
Demo form fills out. Sales lives in HubSpot. Closing the gap with the HubSpot API and a queued listener — and the API choice that determines half the work.
Most form integrations are one-way. This one runs both directions — submissions to Airtable, status changes back. The full loop in a Laravel app.
For solo devs and small teams, Slack pricing isn't worth it just to know someone signed up. Discord's free webhook does the job — here's the listener.
Sales lives in Notion. Submissions live in MySQL. Bridging the two without paying Zapier — a queued listener, the Notion API, and one mapping table.
The sales team lives in Slack. Your form submissions live in a database. This post bridges the gap — and shows what we got wrong on the first version.
Laravel form webhooks are the universal escape hatch — one HTTP POST that lets a submission trigger anything downstream. Here's how FilaForms ships them reliably.
Your marketing person doesn't want to log into your admin panel. Your sales lead doesn't care about Filament. They want a spreadsheet. And honestly, that's
Sometimes a form needs to collect money, not just data. Registration fees, order payments, donation amounts. If you're running FilaForms on your own server, you probably don't want to bolt on a separate payment system and duct-tape it to your form submissions. Stripe Connect lets you handle the w...
