Every serious CRM was built decades ago and never fully rebuilt.

Lumenbase is a new CRM for the AI age that helps you prioritize your day and engage with the right people in your network.

Full-funnel CRM with lists, leads, deals, and accounts; Lumo AI for daily priorities and outreach; automations, lead scoring, forecasting, and integrations with Gmail, Outlook, Slack, LinkedIn, and more.

Try for free · Features · How it works · AI site digest

    Lumenbase

    Zapier Integration Setup

    Automation

    Connect Lumenbase to 6,000+ apps using Zapier webhooks and automations.

    By Sebastian StreiffertPublished Jan 10, 2026Updated May 29, 20267 min read

    Why Zapier?

    Zapier connects Lumenbase to over 6,000 other applications without writing code. Want new deals to appear in a Slack channel? Done. Need form submissions to create contacts? Easy. Looking to sync data with your accounting software? Possible.

    The integration works through webhooks and API calls. Lumenbase sends data to Zapier when things happen (triggers), and Zapier can push data back to Lumenbase when instructed (actions). You build the connection logic in Zapier's visual editor. For more on webhooks and API access, see the API Reference.

    Zapier requires a Zapier account (free tier available with limitations). Lumenbase provides the API access; Zapier handles the orchestration.

    What You Can Automate

    Before diving into setup, here are real examples of Zaps teams commonly build:

    Form to Contact

    Typeform, Jotform, or Google Forms submission creates a new contact in Lumenbase with form fields mapped to contact properties.

    Deal Notifications

    When a deal moves to "Closed Won," post a celebration message to Slack (see Slack integration) and create a row in a Google Sheet for the sales team.

    Lead Enrichment

    New contact created? Zapier calls Clearbit or another enrichment service, then updates the contact with company data.

    Calendar Sync

    Calendly meeting booked? Create an activity in Lumenbase and link it to the relevant contact based on email address.

    The pattern is always: trigger event (something happens) plus action (do something in response). Zapier strings these together into "Zaps."

    Generating Your API Key

    Zapier needs an API key to authenticate with Lumenbase. Generate one in your workspace settings.

    1. Navigate to Settings → Company Settings → Integrations → API
    2. Click 'Generate New Key' and give it a descriptive name like 'Zapier Production'
    3. Copy the key immediately. You will not see it again after closing the dialog.
    4. Store the key somewhere secure. You will paste it into Zapier during setup.
    Treat API keys like passwords. Do not share them in emails, Slack messages, or support tickets. If a key is compromised, revoke it immediately and generate a new one.

    Creating Your First Zap

    Let's walk through a common use case: creating a Lumenbase contact when someone submits a form.

    1

    Start a New Zap

    Log into Zapier and click "Create Zap." You will see the two-step editor: Trigger on the left, Action on the right.
    2

    Configure the Trigger

    Search for your form tool (Typeform, Google Forms, etc.) and select "New Response" or equivalent as the trigger event. Connect your account and select the specific form.
    3

    Add the Lumenbase Action

    For the action step, search for "Webhooks by Zapier" (if Lumenbase is not a native Zapier app) and select "POST" as the action event.
    4

    Configure the Webhook

    Set the URL to your Lumenbase Contact Ingest endpoint and add your API key in the headers:

    Webhook URL
    https://api.lumenbase.io/functions/v1/public-contacts

    Set the payload type to JSON. Add a header: Authorization: Bearer YOUR_API_KEY (use your Lumenbase API key from Settings → Integrations → API).

    5

    Map Form Fields

    In the data section, map your form fields to Lumenbase contact properties. For example:
    Lumenbase FieldForm Field
    first_nameName (first part)
    last_nameName (last part)
    emailEmail Address
    phonePhone Number
    6

    Test and Publish

    Run the test to verify data flows correctly. Check Lumenbase to confirm the contact was created. If everything works, turn on the Zap.

    Using Webhooks for Triggers

    Want Lumenbase events to trigger Zaps? You will need to set up outbound webhooks. When something happens in Lumenbase (deal created, stage changed, etc.), the system sends a POST request to a Zapier webhook URL.

    Setting Up Outbound Webhooks

    1. In Zapier, create a new Zap with 'Webhooks by Zapier' as the trigger
    2. Select 'Catch Hook' as the trigger event. Zapier generates a unique URL.
    3. Copy that URL and paste it in Lumenbase: Settings → Company Settings → Integrations → Webhooks
    4. Select which events should trigger the webhook (deal created, contact updated, etc.)
    5. Save the webhook configuration

    Available Trigger Events

    EventWhen It Fires
    contact.createdNew contact added
    contact.updatedContact field changed
    company.createdNew company added
    deal.createdNew deal added to pipeline
    deal.stage_changedDeal moved to different stage
    deal.closed_wonDeal marked as won
    deal.closed_lostDeal marked as lost
    task.completedTask marked complete
    Be selective about which events trigger webhooks. Sending every contact update to Zapier can consume your Zapier task quota quickly.

    Common Zap Templates

    These patterns solve problems many teams encounter. Adapt them to your specific tools.

    CRM to Slack Notifications

    • Trigger: Deal stage changed to 'Closed Won' (via webhook)
    • Action: Post message to Slack channel with deal name, value, and owner
    • Variation: Different channels for different deal sizes or teams

    Form to Lead Creation

    • Trigger: New form submission (Typeform, Gravity Forms, etc.)
    • Action: Create contact in Lumenbase via API
    • Optional: Create associated company if company name provided
    • Optional: Assign to lead stage based on form source

    Meeting Booked Activity

    • Trigger: New Calendly or other scheduling-tool meeting booked
    • Action: Find matching contact in Lumenbase by email
    • Action: Create activity linked to that contact
    • Optional: Update contact's last activity date or LumenScore

    Spreadsheet Sync

    • Trigger: Deal closed won (via webhook)
    • Action: Add row to Google Sheets with deal data
    • Use case: Finance team tracks closed revenue in a spreadsheet

    Troubleshooting Common Issues

    Most Zap problems fall into a few categories. Here's how to diagnose and fix them:

    ProblemLikely CauseSolution
    Zap not firingTrigger event not configured correctlyVerify webhook URL is saved in Lumenbase; check event type matches
    401 UnauthorizedInvalid or expired API keyGenerate a new API key and update the Zap
    Missing dataField mapping incorrectCheck that Zapier field references match Lumenbase field names exactly
    Duplicate recordsZap triggering multiple timesAdd filters to prevent duplicates; check for multiple webhook subscriptions
    Delayed executionZapier polling intervalUpgrade Zapier plan for faster polling, or use webhooks instead
    Zapier's Task History shows every Zap execution with detailed logs. Check there first when debugging. You can see exactly what data was received and what was sent.

    Best Practices

    These guidelines help Zaps run reliably without burning through your Zapier quota:

    • Use filters liberally. If you only want deals over $10K to trigger a Zap, add a filter rather than letting all deals through.
    • Name Zaps descriptively. "Typeform → Lumenbase Contact (Marketing Site)" beats "My Zap" when you have 20 automations running.
    • Test with real data. Zapier's test feature uses sample data. Before going live, manually trigger the real event and verify the full flow.
    • Monitor task usage. Each Zap execution consumes Zapier tasks. High-volume triggers (every contact update) can exhaust monthly quotas quickly.
    • Document your Zaps. Use Zapier's description field to note what the Zap does and why it exists. Helpful when revisiting months later.
    • Set up error notifications. Zapier can email you when Zaps fail. Enable this so you catch broken automations before they cause problems.

    Quick Reference

    API Keys: Settings → Company Settings → Integrations → API
    Outbound Webhooks: Settings → Company Settings → Integrations → Webhooks
    Zapier Dashboard: zapier.com/app/zaps
    Webhook Trigger: Webhooks by Zapier → Catch Hook
    API Action: Webhooks by Zapier → POST

    Was this article helpful?