Afterplots

FeaturesIntegrations

Connect your stack

Push neighbors and permit signals where your stack already lives

Integrations is where Afterplots meets the rest of your tools. On Growth and Scale, wire signed CRM webhooks, Slack alerts, audience segments, and ad-platform CSVs. On Starter and above, export the canonical permit layer for your territory — GeoJSON or CSV, optional map bounds, and a dedicated webhook with delivery logging.

Open IntegrationsCreate accountAll features

How operators use it

  1. Step 1

    Set your business location

    Profile business location drives which permit territory applies — you only see and export the metro that matches where you operate, not a menu of unrelated cities.

  2. Step 2

    Wire webhooks

    CRM and Slack for marketing moments on Growth+; a separate permit layer URL on Starter+ for permit_layer.export.completed when a geocoded export finishes.

  3. Step 3

    Export with guardrails

    Preview audience CSVs, download permit GeoJSON or CSV (optionally clipped to a bbox), and open the webhook log if a delivery needs attention — retries run automatically when cron is configured.

What it does

Each capability below is a real surface in the Integrations screen — exactly what the team will see and use the first day they sign in.

  • Permit layer export (Starter+)

    Download canonical permit_records with geocoded points for your service area as GeoJSON or CSV. Territory comes from your profile business location — San Diego operators do not see Charleston in a dropdown. Rows are public GIS and web triage signals, not government certification.

  • Optional map bounding box

    Clip a permit export to a WGS84 bbox (min/max lng and lat) when you only need a submarket — same parameters on the download button and the export API.

  • Permit layer webhook and delivery log

    Save a dedicated HTTPS URL and optional HMAC secret for permit_layer.export.completed. Each export job records every POST attempt; open Webhook log on the Integrations tab to see status codes and errors. Failed deliveries retry in-app, then on a schedule, with the same event_id for idempotency.

  • Workspace export limits

    Permit layer exports respect per-workspace caps (feature count per job and daily export count) with plain-language errors — so ops teams know when to narrow a bbox or wait until tomorrow.

  • CRM webhook with a shared-secret signature

    Paste your webhook URL and an optional shared secret, then pick which moments fire a ping — a landing page view, a QR scan, chat started, lead captured, consult booked, a finished audience export, a postcard ready at the printer, or a block that just lit up with new activity. Run a test send to confirm everything is wired correctly.

  • Slack Incoming Webhook

    Paste a Slack Incoming Webhook URL, pick which events should ping the channel (the same event set as the CRM webhook), save, and run a test message. Slack and your CRM run in parallel — no either/or.

  • Audience segments with rules

    Create named segments with rules: county parcel required, landing page required, marketing consent required, normalized contact required, plus a created-date range. Segments are first-class objects you reuse in exports.

  • Suppression list

    Maintain a workspace suppression list keyed on normalized email and phone with optional notes. Suppressions are honored on audience exports so do-not-contact stays do-not-contact across the stack.

  • Neighbor List row data for exports

    Saved rows carry assessor owner names plus email and phone when Lead enrich finds them — the same fields audience CSVs and CRM hand-offs read. Edit contacts from the Neighbor List when you need to correct a match.

  • Audience exports for the major ad platforms

    Run exports to Generic CRM, Google Customer Match, Meta custom audience, and LinkedIn matched-list shapes — each with the right columns and hashing rules. Pick selected row vs. full list and apply a segment before previewing.

  • Live preview before download

    Every audience export starts with a masked preview so you see the row count and a sample of how columns will land before you commit to a download or a webhook delivery.

  • Secure audience downloads and CRM ping on completion

    Completed audience exports give you secure download links that expire after a set time. Optional CRM webhook delivery pings your stack the moment a job finishes; delivery attempts are logged with automatic retries when something fails.

  • 14-day metrics and job history

    A rolling 14-day metrics tile tracks how many audience exports ran, how many rows shipped, how many were suppressed, and how your CRM deliveries did (succeeded, retried, failed). The export history lets you reopen downloads and audit prior runs at any time.

Your CRM stays the source of truth

Afterplots is the workflow that fills the queue and produces the assets; your CRM, maps stack, ad platforms, and Slack are where the team already lives. Integrations is the bridge — signed, territory-aware, and policy-aware.

Availability

Permit layer export (GeoJSON/CSV, bbox, permit webhook) unlocks on Starter, Growth, Scale, and Legacy. CRM webhooks, Slack, segments, and audience exports unlock on Growth and Scale. Free workspaces see contextual upsell on the same screen.

Pairs well with

Create accountSign in to consoleAll features

All featuresUse casesHome

Integrations — CRM, Slack, audiences, permit layer | Afterplots