Integrations
Connect Pipedrive, Brevo, Google Calendar, and webhooks to power your automations.
The Integrations tab in Settings is where you authenticate the external services Nomow works with. Connecting a service here unlocks it as an option inside individual forms, booking pages, and campaign settings — the connection must exist at the workspace level before it can be used anywhere else.
Go to Settings → Integrations in the sidebar.
Pipedrive
Nomow can push deals and contacts to Pipedrive automatically when a form is submitted or a booking is made.
Generate a personal API token in your Pipedrive account under Settings → Personal preferences → API. Paste it into the API token field in Nomow.
Select the Pipedrive pipeline and stage where new deals should land unless a form overrides them. Individual forms can specify their own target pipeline and stage under the form's Integrations step.
Nomow tests the token on save. A green status indicator confirms a successful connection.
Once connected, forms that have Pipedrive enabled will auto-create a deal in Pipedrive on every submission. The contact's fields, source, and UTM data are forwarded as notes on the deal.
Brevo
Brevo handles email sending (transactional and campaign) and list management.
Find your Brevo API key under SMTP & API → API Keys in Brevo. Paste it here.
Choose the Brevo contact list that new contacts should be added to by default. Individual forms can override this with a different list.
Nomow validates the key and loads your Brevo lists. A failure here usually means the key is read-only — Brevo API keys must have contacts:write scope.
Google Calendar
Google Calendar integration is per user, not per workspace — each teammate connects their own Google account so that bookings land on their personal calendar.
Each user who hosts bookings must complete this step individually. The button is shown for the currently signed-in user.
Nomow requests calendar read/write access. Grant access to the Google account that owns the calendar you want to use.
After authorization, choose which calendar events should be created on. This is the calendar Nomow writes to when a booking is confirmed.
Once connected, booking pages that list this user as a host will create Google Calendar events automatically and send attendees a Google Meet link if the booking page's location is set to Google Meet.
Webhooks
Webhooks let you push Nomow events to any external URL — a Zapier catch, a Make scenario, or your own API.
| Field | Purpose |
|---|---|
| URL | The HTTPS endpoint that receives the POST request |
| Secret | Optional; Nomow signs each payload with HMAC-SHA256 using this secret so you can verify authenticity |
| Events | Checkboxes for the event types to send: form_submit, booking_created, contact_created, deal_created, and others |
Nomow retries failed webhook deliveries up to three times with exponential backoff. After three failures, the delivery is marked as dropped and logged.
Next steps
With integrations connected, configure what happens after a form submission in Post-submission actions, or set up your booking pages in Create a booking page.
Was this article helpful?