Book a demo Start free trial
All guides

Integrations

Zapier, Make and n8n — recipes with the Letfold API and webhooks

Connect Letfold to thousands of other apps without code: webhooks in, API calls out. Five recipes to copy.

How it works

Zapier, Make (formerly Integromat) and n8n all do the same two things with Letfold:

  • Trigger on an Letfold webhook: new enquiry, viewing booked, repair reported, rent paid, certificate expiring and more.
  • Act by calling the Letfold API with your API key: create an enquiry, book a viewing, add a task, read a property.

You need an API key and, for triggers, a webhook endpoint. Both come from Settings → API & webhooks. The full reference, authentication and the sandbox are at /developers.

If those cards say Coming soon, the API is launching this week; the recipes below will work unchanged once it is live.

Recipe 1: website form → Letfold enquiry (Zapier)

  1. Trigger: your form app (Typeform, Gravity Forms, Webflow Forms…) New submission.
  2. Action: Webhooks by Zapier → POST to https://letfold.com/api/v1/leads with header Authorization: Bearer YOUR-KEY and a JSON body: full_name, email, phone, message, optionally property_id.
  3. Test, switch on. Each submission becomes an enquiry in the right branch.

Recipe 2: new enquiry → Google Sheet row (Make)

  1. In Letfold, add a webhook endpoint with the URL Make gives you for a Custom webhook module, subscribed to enquiry.created.
  2. In Make: Custom webhook → Google Sheets: Add a row, mapping full_name, email, property.address and created_at.

Recipe 3: viewing booked → SMS to the viewer (n8n)

  1. Webhook node receiving viewing.booked from Letfold.
  2. Twilio (or your SMS provider) node sending "Your viewing at {{address}} is confirmed for {{starts_at}}". (Letfold's own Twilio integration already sends confirmations if you prefer.)

Recipe 4: repair reported → Trello / Asana card

Webhook maintenance.reported → create a card with the title, the tenant's description and a link to the ticket; add the Letfold ticket id to the card so you can close the loop.

Recipe 5: rent paid → accounting line

Webhook rent.paid → append to your bookkeeping tool (Xero and QuickBooks have native Zapier actions). Note: rent is client money, not your income; book it to the client account.

Signatures

Every webhook is signed (webhook-id, webhook-timestamp, webhook-signature, HMAC-SHA256). Zapier and Make can ignore the signature on a private URL; in n8n verify it with a Crypto node when the workflow is exposed publicly.

Last updated 11 Nov 2026

Need help with this? [email protected]