How to connect Make.com to Twentybaan

Video tutorial

The video shows the real Integrations page in Twentybaan. The written guide below keeps the exact scopes, API references, and optional pull workflow in one place.

Why this matters

Make.com becomes much easier to reason about when you split the setup into two clear jobs.

• Real-time events: Twentybaan sends a webhook to your Make.com scenario the moment something important happens, for example a new inquiry.
• Scheduled pulls: Make.com uses your API key to fetch data like listings on a schedule when you need periodic syncs or reports.

Most teams should start with the webhook path first, because it is faster to validate and immediately useful. Add scheduled pulls only when you need them.

TL;DR

• Open Settings -> Integrations in Twentybaan.
• Create an API key only if your Make.com scenario also needs scheduled reads from the API.
• In Make.com, create a Webhooks -> Custom webhook module and copy the webhook URL.
• Paste that URL into the Twentybaan webhook form, keep New inquiry enabled first, and add more events only when the first flow is proven.
• Use the written API references below for the optional /v1/me/ and /v1/listings/ checks.

Prerequisites

• A Twentybaan lister account that can open Settings -> Integrations.
• A Make.com scenario with Webhooks -> Custom webhook available.
• If you also want scheduled pulls, a Make.com HTTP -> Make a request module.
• The right scopes on your Twentybaan API key:
• read:me for the first authentication check.
• read:listings only if you really need scheduled listing pulls.

staging.twentybaan.com/account/settings/integrations

Step 1, create the API key only for the data you need

If your Make.com scenario only needs real-time webhook delivery, you can start with the webhook form and skip the API key for now. Create the API key when you also need scheduled reads from Twentybaan.

• Use a clear label, for example Make.com listings sync.
• Keep the scopes narrow. Start with read:me and add read:listings only when the scenario actually needs listings.
• Do not create extra keys for every experiment. Revoke old staging keys after testing.

staging.twentybaan.com/account/settings/integrations

Step 2, add your Make.com webhook URL and choose events

This is the fastest real-time path. In Make.com, create a Custom webhook, copy the generated URL, and paste it into the Twentybaan webhook form.

1. Paste the Make.com webhook URL into Webhook URL (https).
2. Keep New inquiry enabled first. It is the easiest first event to validate.
3. Add Listing published or Listing updated only after the first end-to-end test is green.
4. Use Add webhook, then run one test from a staging-safe inquiry flow before you expand the scenario.

staging.twentybaan.com/account/settings/integrations

Step 3, add the optional scheduled pull path only if you need it

When Make.com should fetch data on a cadence, verify the API key first and only then add the listings request.

Make.com module: HTTP -> Make a request

Method: GET
URL: https://api.twentybaan.com/v1/me/

Headers:
  Accept: application/json
  Authorization: Bearer YOUR_API_KEY

curl https://api.twentybaan.com/v1/me/ \
  -H "Accept: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY"

Reference docs: https://api.twentybaan.com/me/?lang=zh&v=20260307a and https://api.twentybaan.com/authentication/?lang=zh&v=20260307a

Make.com module: HTTP -> Make a request

Method: GET
URL: https://api.twentybaan.com/v1/listings/

Query string:
  limit=10

Headers:
  Accept: application/json
  Authorization: Bearer YOUR_API_KEY

curl -G https://api.twentybaan.com/v1/listings/ \
  -H "Accept: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d limit=10

Reference docs: https://api.twentybaan.com/listings/?lang=zh&v=20260307a

If you want the provider-managed webhook endpoints later, continue with Webhook subscriptions after the simpler UI webhook path is already working.

Troubleshooting

• The Integrations page says it is not enabled yet: your lister account does not have the Integrations package enabled. Fix that first.
• Make.com never receives the event: re-check the webhook URL, keep only one event enabled first, and use a staging-safe test action you can reproduce quickly.
• 401 Unauthorized: your API key is missing, revoked, or sent in the wrong header. Re-run the /v1/me/ check first.
• 403 Forbidden: the key is valid, but the scope is missing. Add the exact scope you need, especially read:listings.
• 429 Too Many Requests: your Make.com polling schedule is too aggressive. Slow the schedule down or move that part to webhooks.

Reference docs: https://api.twentybaan.com/errors/?lang=zh&v=20260307a

Next steps

1. Once the first Make.com webhook run is green, add the second event you actually need.
2. If you need scheduled data, continue with API quickstart and Listings.
3. If you want provider-managed subscriptions later, open Webhook subscriptions.
4. If you get stuck, include the exact Make.com module type, the event you selected, and the HTTP status or delivery result when you ask for help.

Last updated

2026-03-10 UTC