Zapier Integration Setup
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.
What You Can Automate
Before diving into setup, here are real examples of Zaps teams commonly build:
Form to Contact
Deal Notifications
Lead Enrichment
Calendar Sync
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.
- Navigate to Settings → Company Settings → Integrations → API
- Click 'Generate New Key' and give it a descriptive name like 'Zapier Production'
- Copy the key immediately. You will not see it again after closing the dialog.
- Store the key somewhere secure. You will paste it into Zapier during setup.
Creating Your First Zap
Let's walk through a common use case: creating a Lumenbase contact when someone submits a form.
Start a New Zap
Configure the Trigger
Add the Lumenbase Action
Configure the Webhook
Set the URL to your Lumenbase Contact Ingest endpoint and add your API key in the headers:
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).
Map Form Fields
| Lumenbase Field | Form Field |
|---|---|
| first_name | Name (first part) |
| last_name | Name (last part) |
| Email Address | |
| phone | Phone Number |
Test and Publish
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
- In Zapier, create a new Zap with 'Webhooks by Zapier' as the trigger
- Select 'Catch Hook' as the trigger event. Zapier generates a unique URL.
- Copy that URL and paste it in Lumenbase: Settings → Company Settings → Integrations → Webhooks
- Select which events should trigger the webhook (deal created, contact updated, etc.)
- Save the webhook configuration
Available Trigger Events
| Event | When It Fires |
|---|---|
| contact.created | New contact added |
| contact.updated | Contact field changed |
| company.created | New company added |
| deal.created | New deal added to pipeline |
| deal.stage_changed | Deal moved to different stage |
| deal.closed_won | Deal marked as won |
| deal.closed_lost | Deal marked as lost |
| task.completed | Task marked complete |
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:
| Problem | Likely Cause | Solution |
|---|---|---|
| Zap not firing | Trigger event not configured correctly | Verify webhook URL is saved in Lumenbase; check event type matches |
| 401 Unauthorized | Invalid or expired API key | Generate a new API key and update the Zap |
| Missing data | Field mapping incorrect | Check that Zapier field references match Lumenbase field names exactly |
| Duplicate records | Zap triggering multiple times | Add filters to prevent duplicates; check for multiple webhook subscriptions |
| Delayed execution | Zapier polling interval | Upgrade Zapier plan for faster polling, or use webhooks instead |
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
Was this article helpful?