Skip to content
Integrations

Connect Zapier & Make without code

OXIAE doesn’t have a dedicated app in the Zapier or Make directory. Instead, our open REST API and signed webhooks plug straight into each platform’s own Webhooks and HTTP modules, so you can connect OXIAE to thousands of other tools in a few clicks, from Google Sheets and Slack to Facebook Lead Ads and your project tool. No developer, no server, no maintenance: you build a workflow visually and set it live.

The most important thing doesn’t change in the process. Whether a request comes in via the API directly or via a Zap or scenario: provenance and consent travel along by default, and your audit trail stays complete. Zapier and Make are the fast pass-through on top of the same auditable infrastructure.

Book a demo To the docs

What you can build without code

Zapier and Make are no-code automation platforms: you connect apps to each other in a visual builder and decide for yourself what happens when something changes in OXIAE, or when you want to submit a request to OXIAE instead. Because both platforms offer generic Webhooks and HTTP modules, you can wire OXIAE’s REST API and signed webhooks to virtually any of the thousands of tools they already support, from your CRM to your forms and landing pages.

Forward & report

Write accepted requests to Sheets, Airtable or a data warehouse and send notifications to Slack or email.

Submit from any source

Let requests from Facebook Lead Ads, Typeform or your own forms come into OXIAE with consent and provenance.

Automate follow-up

Create tasks, schedule follow-up or update records in your CRM as soon as a match is found or a payout is processed.

Webhook events you can catch

These are the signed webhooks OXIAE can send. Catch any of them with Zapier’s “Webhooks by Zapier” trigger or Make’s Webhooks module to start your Zap or scenario. Every event delivers the request as structured fields, including provenance and consent, so you can pass them straight to the next step.

New request received

OXIAE sends a signed webhook the moment a new request comes in and has passed the first validation. Catch it with Zapier’s “Webhooks by Zapier” trigger or Make’s Webhooks module, and you receive the full lead, including provenance and consent, as structured fields.

lead.received

Consent recorded

A signed webhook fires the moment the requester’s consent is registered, with the exact consent text, the timestamp and the source. Ideal for writing consent into your own records.

consent.recorded

Match found

A signed webhook fires as soon as the routing rules have matched a request to a buyer. Handy for starting a task, notification or follow-up in your project tool or CRM.

match.found

Payout processed

A signed webhook fires when a payout or acceptance has been completed and booked into the audit trail. Perfect for your financial administration or a weekly overview.

payout.processed

REST API calls you can make

These are the REST API endpoints you can call from Zapier’s “Webhooks by Zapier” action or Make’s HTTP module. That way you don’t just receive data out of OXIAE, you also feed data into it, for example to submit requests from an external source.

Create / submit request

Call this endpoint from Zapier’s “Webhooks by Zapier” action or Make’s HTTP module to create a new request in OXIAE from another source, for example a Facebook Lead Ads form, a Typeform or a row in a spreadsheet. You pass along contact details, provenance and the consent text, so the lead comes in with valid consent.

POST /v1/requests

Look up status

Call this endpoint to retrieve the current status of an existing request (received, accepted, matched, paid out), so you can update your own systems or determine a follow-up action.

GET /v1/requests/{id}

Authentication with an API key

Connecting OXIAE to Zapier or Make is a matter of a single key. You create an API key in OXIAE and add it as a header in Zapier’s “Webhooks by Zapier” step or Make’s HTTP module, and you’re done. From that moment you can catch OXIAE’s webhook events and call the REST API in any Zap or scenario.

Keys are scoped: you decide which permissions a key gets, read only, submit only, or both. Want to stop using it? You revoke the key and access is broken immediately, without having to rebuild your Zaps.

All connections run encrypted over TLS. You can find the full steps in the documentation.

Set up connection API key 
# Authentication for Zapier / Make
# Step 1: generate an API key in OXIAE

API base URL : https://api.oxiae.com/v1
Auth header  : Authorization: Bearer sk_live_…

# OXIAE has no dedicated app in the Zapier or Make directory.
# In Zapier, add this header inside a “Webhooks by Zapier” step,
# or use the same tool to catch inbound webhooks.
# In Make, add it under Headers in the HTTP module, or catch
# inbound events with the Webhooks module.
# Keys are scoped: give a key only the permissions it needs
# (read, submit, or both) and revoke it again at any moment.

Example recipes

Concrete scenarios say more than a list of possibilities. These are three commonly used Zaps and Make scenarios that you can rebuild in fifteen minutes, with provenance and consent travelling along everywhere in them.

Reporting

New accepted request → Google Sheets + Slack

Trigger

match.found webhook

  1. 1 OXIAE: signed webhook match.found, caught with Webhooks by Zapier / Make’s HTTP module
  2. 2 Google Sheets: add a row with name, source, campaign and consent timestamp
  3. 3 Slack: message to #sales with a short summary

Your team sees in real time which requests have been accepted, with the provenance right next to them, without anyone retyping by hand.

Lead submission

Facebook Lead Ads → OXIAE with consent & provenance

Trigger

New lead in Facebook Lead Ads

  1. 1 Facebook Lead Ads: new lead
  2. 2 Formatter: convert the checkbox consent into the consent text
  3. 3 OXIAE: POST /v1/requests via Webhooks by Zapier / Make’s HTTP module, with contact, source, campaign and consent

The campaign and ad account come along as provenance; the consent from your form is recorded as consent. That way the lead is demonstrably compliant from the moment it arrives.

Follow-up

Match found → task in your project tool

Trigger

match.found webhook

  1. 1 OXIAE: signed webhook match.found, caught with Webhooks by Zapier / Make’s HTTP module
  2. 2 Filter: only for a specific label or buyer
  3. 3 Asana / Trello / ClickUp: create a task with deadline and context

Every matched request automatically becomes an action for the right colleague, with provenance and consent as context in the task description.

Building your first Zap or scenario

From a blank canvas to a live automation in four clear steps. You always test with real fields first before anything runs in production.

01

Connect OXIAE

Create a scoped API key in OXIAE and add it as a header in Zapier’s “Webhooks by Zapier” step or Make’s HTTP module. Set it up once, then reuse it across all your Zaps and scenarios.

02

Choose a webhook event or API call

Start with a webhook event (for example “match.found”) if you want to automate from OXIAE, or with a REST API call to POST /v1/requests if you want to submit leads instead.

03

Map the fields

Drag the OXIAE fields to the right place in your target tool. Give provenance and consent their own explicit column or field, so consent travels along demonstrably.

04

Test & go live

Run a test with a real request and check that everything is correct. Happy with it? Turn the Zap or scenario on: from that moment everything runs automatically.

Which fields you get back

On every webhook event, Zapier or Make receives the request as separate, reusable fields. Below you see what the payload for the “match.found” event looks like, with provenance and consent as separate blocks you can map straight away.

Webhook payload match.found 
// Example: fields you receive in the webhook body
// for the event "match.found"
{
  "lead_id": "lead_8f21",
  "status": "accepted",
  "contact": {
    "name": "Sanne de Vries",
    "email": "sanne@example.com",
    "phone": "+31 6 12345678"
  },
  "provenance": {
    "source": "facebook-lead-ads",
    "campaign": "legal-aid-q2",
    "label": "legal-desk"
  },
  "consent": {
    "given": true,
    "text": "I consent to being contacted.",
    "timestamp": "2026-03-12T09:41:07Z",
    "ip": "84.12.x.x"
  }
}

Provenance & consent travel along, also via Zapier and Make

No-code should never mean you give up compliance as a lead generator. That’s why your platform treats a Zap or Make scenario exactly like a direct API connection: the provenance and the consent evidence travel along by default, in both directions, recorded GDPR-compliant in your audit trail.

Consent as its own fields

In every webhook OXIAE delivers the consent as separate fields: given (yes/no), the exact text, the timestamp and the IP address. You don’t need to parse anything: you map them straight to the right place in your target tool.

Provenance travels along

Source, campaign, label and landing page come along as separate fields. Whether you write to Sheets, a CRM or a database: you always know where the request came from.

Audit trail stays complete

A Zap or scenario changes nothing about the source of truth. The full audit trail stays in OXIAE; Zapier and Make are a pass-through, not a replacement for your record-keeping.

Consent on submission

When you submit a request through the REST API from Zapier or Make, you pass the consent text and the timestamp in the request body. OXIAE records that consent, exactly as it does with a direct API connection.

Zapier / Make or the native connection?

No-code is ideal to get started quickly and connect individual tools. If you need high volume, tight latency requirements or complex logic, you’re better off choosing the native API or a custom connection.

When Zapier / Make
When native API or custom
You want something live quickly without a developer.
You already have a development team and want full control.
Limited to medium volume of requests.
High volume or tight real-time and latency requirements.
Standard forwarding, reporting and follow-up.
Complex transformations, custom retry and error handling.
You connect individual, popular tools to each other.
Deep integration into a legacy CRM or data warehouse.

API & webhooks

Want the full control of a direct connection? Build exactly the flow you need with the REST API and signed webhooks.

View API & webhooks

Custom integration

No standard connection fits and you don’t want to build it yourself? Let us build a custom integration into your platform.

View custom integration

Frequently asked questions about Zapier & Make

The questions we get most often from teams connecting OXIAE no-code to their stack.

Do I need a developer to set this up?

No. Zapier and Make are no-code platforms: you build a workflow visually by connecting blocks to each other, including their built-in Webhooks and HTTP modules. All you need is an OXIAE API key, which you set up in a few clicks and add as a header. If you do want to go deeper into the technical side, you can always switch to the native API or a custom build.

Which webhook events and API calls are available?

As webhook events you can catch: lead.received, consent.recorded, match.found and payout.processed, each delivered as a signed HMAC webhook. As REST API calls you can create/submit a request (POST /v1/requests) and look up the status of an existing request (GET /v1/requests/{id}). Since OXIAE has no dedicated app in the Zapier or Make directory, you wire these up yourself with each platform’s generic Webhooks or HTTP module.

Doesn’t consent get lost via Zapier or Make?

No. On every webhook OXIAE delivers the consent as separate fields (given, text, timestamp and IP) which you map straight to your target tool. When you submit a request via the REST API from Zapier or Make, you pass the consent text and the timestamp in the request body, and OXIAE records that consent. The audit trail in OXIAE remains the full source of truth either way.

Are there rate limits?

Yes, the API has rate limits to safeguard stability. For normal Zapier and Make use you won’t notice them. If you expect very high volume or many concurrent runs, that’s exactly the moment to consider the native API or a custom connection; with those you have more control over throughput and error handling.

What does this cost?

OXIAE charges nothing extra for connecting to Zapier or Make: you use your ordinary API key. You do need a subscription to Zapier or Make; the cost of that depends on the number of tasks or operations you run per month. For many teams a starter subscription is enough to begin with a few Zaps.

Can I submit requests from Facebook Lead Ads automatically?

Yes. A commonly used recipe connects Facebook Lead Ads to the OXIAE REST API endpoint POST /v1/requests, via Zapier’s “Webhooks by Zapier” action or Make’s HTTP module. The campaign and the ad account come along as provenance, and the consent from your lead form is recorded as consent. That way the lead is demonstrably compliant from the very first moment.

When am I better off choosing the native API?

Choose the native API or a custom connection for high volume, tight latency requirements, complex transformations or deep integration into a legacy system. For that, see the API & webhooks and Custom integration pages; for getting started quickly and connecting individual tools, Zapier and Make remain the easiest route.

Read more

Automate your lead flow without code

Book a demo and see how you connect OXIAE to your entire stack via Zapier or Make, with provenance and consent that travel along by default.

Book a demo Log in