Mattermost integration

Your team chats on a Mattermost server you run, not someone else's cloud. Post every lead into the right channel as a clean table, with an @here when it needs a call now.

  • Webhook
  • Landing pages, Quiz funnels, Workflows (beta, by HTTP Request)

Why connect it

Why Mattermost and LanderLab

  • Lead alerts on a server you control

    The alert goes from the page to your own Mattermost server, with no chat vendor or automation service in between.

  • Readable tables, not raw fields

    Mattermost posts Markdown, tables included. Each lead becomes a two-column table of field and answer that reads well on desktop and mobile.

  • @here when a lead needs a call now

    Start the post with @here and everyone active in the channel is notified, so a hot lead doesn't wait for someone to look.

  • One webhook, a channel per page

    A post can name its channel, so one webhook serves every page, each sending its leads to the team that works them.

  • The campaign and variant on every post

    Hidden fields carry the campaign from the ad's URL and LanderLab adds the A/B variant, so each post says what produced the lead.

Mattermost on your landing pages

Teams pick Mattermost because they want their chat on infrastructure they control: insurance agencies, financial services, healthcare-adjacent lead gen, agencies with strict client data rules. LanderLab posts each lead from a landing page or quiz funnel into a Mattermost channel, so the alert lands on that server, next to the team that works it.

Mattermost incoming webhooks turn a request into a post, and LanderLab's Webhook integration sends one on every submit. There's no plugin to install and no automation service in between handling your leads' phone numbers.

Lead alerts on your own Mattermost server

When your chat runs on your own server, adding a cloud automation tool just to post a notification undoes part of the reason you chose it. LanderLab posts to the Mattermost webhook directly, so the lead goes from the page to your server and nowhere else on the way. LanderLab also keeps the lead in its Leads tab, unless you turn on Lead Compliance Delivery, which sends leads to the integrations without storing them in LanderLab.

One thing to know: LanderLab only sends to HTTPS addresses, so the server has to answer on HTTPS at an address the internet can reach. A server only reachable over your VPN won't receive alerts.

A Markdown table per lead, and @here when it's hot

Mattermost's text is Markdown, tables included, so a lead reads as two clean columns: Field and Answer. Coverage amount, age, tobacco use, the campaign and the variant line up the same way every time, and an agent can quote from the post without opening another screen.

Put @here at the start and everyone active in the channel gets notified. Keep @channel for a channel that exists to be woken up. Long quizzes are fine: Mattermost posts up to 16,383 characters and splits anything longer into consecutive posts.

One Mattermost webhook, a channel per product line

A post can override the webhook's default channel by name, and post to any public channel or to private channels the webhook's creator belongs to. Final expense, term life and Medicare supplement pages can share one webhook while each sends its leads to its own team's channel.

A System Admin can also let posts carry their own username, so alerts appear as Lead alerts rather than the generic webhook name.

Use cases

Ways to use Mattermost on paid traffic

  • 01

    A life insurance agency's quote floor

    Term life quizzes on Facebook post every quote request to the life leads channel with @here. The first agent free replies in the thread, and the coverage amount in the table tells them which carrier to quote.

  • 02

    Separate channels per product line

    Final expense, term and Medicare supplement pages share one webhook, each naming its own channel. Each team sees only its product's leads.

  • 03

    Client leads in an agency's own chat

    An agency that hosts its own Mattermost gives each client a private channel. Pages post there, and the client's staff work leads without the data passing through another chat vendor.

FAQ

Mattermost integration FAQ

Anything not here, ask us.

Mattermost and LanderLab

Is Mattermost a good fit for lead alerts?

If your team already chats on Mattermost, yes, especially when you want lead data to stay on infrastructure you control.

Does LanderLab integrate with Mattermost?

Yes, through the page's Webhook integration: it posts each lead to a Mattermost incoming webhook.

Does it work with a self-hosted Mattermost server?

Yes, as long as the server answers on HTTPS at an address the internet can reach.

Can one webhook post to several channels?

Yes. Each page's post can name its own channel, public or private, as long as the webhook's creator is in the private ones.

Do I need Zapier to post leads to Mattermost?

No. LanderLab calls Mattermost's incoming webhook directly.

Other integrations

Plug in the rest of your stack.

Connect Mattermost and launch your next page.

Build the page, switch Mattermost on and send your ads to it. Free to start, no card.

From one prompt to qualified leads

Watch one prompt become a live solar quote funnel, every lead routed to your buyer, and the leaks flagged before they eat your budget.

0:00
0:59