This is the same guide agents use inside REALM.Get REALMLog in
The Complete Guide

The REALM Guide

Everything Realm does, and how to use it. The full handbook: every feature, with step-by-step instructions. Use the contents on the left to jump to a chapter.

97Chapters
15Product areas

Apps marketplace

Status: live

The Apps page (left menu → Apps) connects Realm to the other tools your business runs on — Slack, Mailchimp, Google Sheets, QuickBooks, your lead portals, and thousands more through Zapier. Enabling an app sets up everything it needs: keys, a webhook slot, and a short recipe.

The three kinds of card

  • Direct connect — Slack and Microsoft Teams. You paste one URL that Slack or Teams itself hands out. No Zapier, nothing else to build.
  • Via Zapier — most cards. Realm does its half natively (signed events out, a scoped key in) and a simple Zap bridges to the tool.
  • Built into Realm — your connected inbox, Authentisign, social publishing, calling and texting. The card links to where each one is managed.

Enabling an app

Click Enable on a card (broker or admin — the key it creates can read your organization's data). The setup panel opens with the app's API key (shown once — copy it) and the step-by-step recipe. Follow the steps; when a card needs a webhook URL, paste it and click Connect & send sample.

Choosing what posts

Connected cards have a What posts here section in their Setup panel — check or uncheck event types (new leads, stage changes, document approvals, completed signings) and save. Only the checked events feed that app from then on. A team that wants leads in one Slack channel and closings in another can run the Slack card for one and the general Zapier card (with a filter) for the other.

How you know it's working

Three signals, in order of proof:

  1. The sample event. The moment you click Connect & send sample, Realm sends a real event through the real pipeline. For Slack or Teams you'll see a message appear in the channel immediately. For a Zapier card, the sample is waiting when you click **Find new records** in the Zap's Test tab.
  2. Send test, any time. Every connected card has a Send test button. It fires a sample shaped like that card's real events through the same path real events take — "Delivered" on the card plus the test arriving in the destination is proof the whole chain works.
  3. The health chip. Once real events flow, the card reads Active · N events / 30d. That's live delivery telemetry, not a cached status.

The definitive end-to-end test is a real action: add a test lead (or move a transaction's stage) and watch it arrive in the connected tool within seconds. Delete the test lead afterwards.

When something's wrong

  • "No traffic yet" — connected, but no events have fired. Normal on a fresh connection; use Send test to prove the pipe.
  • "Failing · N of M events" — deliveries are erroring. Check the destination: is the Zap turned ON? Did the URL change?
  • "Paused — check webhook" — the endpoint failed repeatedly and Realm stopped sending (nothing is silently dropped; deliveries are logged). Fix the destination, then Disable and re-Enable the card to reconnect.
  • A Zapier action test says "filtered out" — if you added the closed-only filter on an accounting card, that's the filter working: the sample isn't a closing. Publish and let the first real closing prove it.

Every delivery — including failures and retries — is listed under Developer → Webhook endpoints → Deliveries at the bottom of the Apps page.

Watch it done

The Academy has walkthroughs: Apps: connect REALM to your other tools, plus worked examples for Slack, portal leads, and Mailchimp (left menu → Learning).