Fondoo
GitHubStart your 7-day trial for $0Start trial
Docs

Connect Make to Fondoo

Live7 min readUpdated

Make (make.com) is a visual automation tool. This connection works the other way round from most Fondoo connections: you add Fondoo into Make with a Fondoo API key. Your Make scenarios can then create and update support tickets, manage contacts, publish sites and create checkout links, and a Fondoo event can start a scenario.

Fondoo provides a Make custom app definition (apps/make-app/fondoo.make.json, MIT licensed). It is not in Make's app directory and has not been imported into any Make account. You create a private custom app in your own Make account and paste the definition in. The definition has not been run inside Make yet, so expect to fix small things.

What Fondoo can do with it

The app has one connection, one instant trigger and 17 action modules.

ModuleFondoo operationAPI key scopes it needs
Watch Events (instant trigger)creates a webhook subscriptionwebhooks:write
Create a Support Ticket / Add an Internal Ticket Note / Update a Ticketsupport_create_ticket / support_add_note / support_update_ticketsupport:write
Reply to a Ticketsupport_replysupport:write, email:write
List Tickets / Get a Ticketsupport_list_tickets / support_get_ticketsupport:read
Create a Contact / Update a Contact / Tag Contactscreate_contact / update_contact / tag_contactscontacts:write
Get a Contactget_contactcontacts:read
Publish a Sitepublish_sitesites:write
Get a Siteget_sitesites:read
List Businesseslist_businessesbusinesses:read
Create a Newsletter Issuecreate_newsletter_issue (creates it, does not send)email:write, pages:write, sites:write, analytics:write
Create a Checkout Linkcreate_checkout_link (does not charge a card)payments:write
List Eventslist_eventsevents:read
Call an Operationany operation in Fondoo's automation list except webhook management, for example send_email, schedule_social_posts, upsert_product, import_subscribers, list_productsthe scopes of that operation

Write modules have Idempotency Key (map something unique, such as the Fondoo event ID, so a re-run cannot repeat the action) and Dry Run (preview only). In Call an Operation, put dryRun or idempotencyKey inside the JSON body. List modules return one bundle that holds the whole list.

The modules show Fondoo's status field. If it is pending_approval (with approvalId and approvalUrl) or connection_required (with provider and connectUrl), the action did not happen. Add a filter so later modules only run when status is empty.

What needs your approval: the same rules as for your agent. Money actions (such as upsert_product) and sensitive support replies wait for the owner. Complaints, refunds and legal tickets stay human-only. Sending a newsletter is always approval-gated.

Before you start

  • A Make account where you can open Custom Apps. Make does not state a plan requirement on the pages we reviewed; check Make's pricing if you don't see the option.
  • Your Fondoo API base URL. Hosted Fondoo: https://api.getfondoo.com (no /v1). It must be HTTPS and reachable from the internet. Make runs in the cloud, so localhost will not work.
  • The file fondoo.make.json from the Fondoo source (apps/make-app).
  • About 30 to 60 minutes to paste the components. You can start with just the connection, Watch Events and Call an Operation, which together cover everything.

Step by step: get your credentials

1. Create the custom app in Make

Make's current steps (create your app, web interface):

  1. Log in to Make. In the left navigation click Custom Apps (you may need to click More first).
  2. Click + Create app in the upper-right corner.
  3. Fill in Name fondoo (lowercase letters, digits and dashes), Label Fondoo, Theme #4f46e5 and an optional description. Click Save.

2. Paste each component

Open the app. Make shows the components in tabs across the top. Copy each part of fondoo.make.json into the matching place. Make's exact tab and field names may differ for your account; the custom apps docs describe each component.

  1. Base: paste the base object. It sends Authorization: Bearer {{connection.apiKey}} and hides that header in logs.
  2. Connections: create a basic connection labeled Fondoo API key. Paste parameters (fields baseUrl and apiKey) and communication. Its test calls the read-only list_event_types (basic connection).
  3. Webhooks: create a dedicated webhook named fondooEvents, attach the Fondoo connection, and paste its parameters, attach and detach (attached webhooks).
  4. Modules: create Watch Events as an Instant trigger linked to the fondooEvents webhook. Create the others as Action modules. For each, paste api (the request), expect (mappable parameters), interface and samples.

3. Create a scoped Fondoo API key

Give the key only the scopes of the modules you use, from the table above. Always include events:read (the connection test uses it). Keys can never get owner or admin access. Fondoo shows the key once. See Connect it in Fondoo.

4. Add the connection in a scenario

Add any Fondoo module, click Add next to Connection, enter the Fondoo API Base URL and API Key, and save. Make runs the test request.

Sharing with others: a private app can only be used by you until it is installed in an organization. To share it outside your organization, Make's Publish button creates an invite link, and a published app cannot be made private or deleted again (app visibility).

Connect it in Fondoo

Make is not a Fondoo connector. You won't find it under Connections, and connect_service({provider:"make"}) does not work. On the Fondoo side you only create an API key.

(a) In the dashboard: open Settings → API keys → Create key. The form currently offers only one read level at a time (Read analytics, Read sites or Read pages). That is not enough for Make, because the connection test needs events:read. Use (b) or (c) until the form offers more. This may differ for your account.

(b) By asking your agent:

Create a Fondoo API key called "Make" with the scopes events:read, webhooks:write, support:read and support:write.

create_api_key({ name: "Make", scopes: ["events:read", "webhooks:write", "support:read", "support:write"] })

For an agent this always returns pending_approval with an approval link. An agent can only grant scopes it holds itself. Only a signed-in human owner can approve, never through MCP. The key appears once in the approval result, so the agent never sees it. Note: approving from the Needs your OK card on the Home page currently shows only "Approved." and not the key. If that happens, revoke the key and use the approval link or option (c). This may differ for your account.

(c) Over REST with an owner key (for example a self-hosted bootstrap owner key). It returns id, key and scopes at once:

POST https://api.getfondoo.com/v1/ops/create_api_key
Authorization: Bearer <owner key>
Content-Type: application/json

{"name":"Make","scopes":["events:read","webhooks:write","support:read","support:write"]}

Workspaces that enforce owner two-factor authentication reject owner keys. Manage keys with list_api_keys (names, scopes, last use) and revoke_api_key({keyId}) (agents need approval), or Settings → API keys → Revoke.

Webhooks

Watch Events uses a Fondoo webhook that Make manages:

  • When you create the webhook in the trigger, Make's attach step calls POST /v1/webhooks (subscribe_webhook) with the Make webhook URL, your Event Types and optional Site ID, and saves the returned webhookId and secret. Leave Event Types empty for all events.
  • When you delete the webhook, the detach step calls DELETE /v1/webhooks/{webhookId} (unsubscribe_webhook).
  • Each delivery becomes one bundle with id, type, version, workspaceId, siteId, createdAt and payload.

Important: Make does not verify Fondoo's signature. Fondoo signs each delivery with Fondoo-Signature: t=<unix seconds>,v1=<hex> (HMAC-SHA256 of <t>.<raw body> with the secret, 300-second tolerance). Make's custom app webhook definition gives no documented way to compute this, so the secret is stored but unused. Keep your Make webhook URL private. Treat each bundle as a notification only: before acting, re-read the record with a Get module (Get a Ticket, Get a Contact, Get a Site). The n8n and Zapier apps do verify signatures.

Type event types exactly as written: ticket.created, ticket.updated, ticket.solved, complaint.opened, refund.requested, csat.received, site.published, page.published, page.updated, deploy.rolled_back, form.submitted, contact.created, contact.updated, contact.deleted, signup.recorded, order.paid, subscription.started, subscription.updated, subscription.canceled, payment.failed, refund.recorded, dispute.opened, email.sent, email.delivered, email.bounced, email.complained, email.opened, email.clicked, email.unsubscribed, post.scheduled, post.published, post.failed, seo.issue.found, seo.issue.resolved, index.status.changed, ranking.changed, alert.raised, approval.requested, approval.decided, usage.threshold.reached, domain.registered, purchase.completed, release.ingested, content.page.generated, operation.completed, asset.uploaded, asset.deleted, webhook.test, entitlement.updated, order.created.

Your agent can also use list_webhooks, list_webhook_deliveries({webhookId}), replay_webhook_delivery({deliveryId}), send_test_event({webhookId}) and rotate_webhook_secret({webhookId}).

Test that it works

  1. Create the Fondoo connection in a scenario. Make's test should pass.
  2. Run Call an Operation with list_event_types and body {}. You should get the event catalog.
  3. Run a write module with Dry Run set to Yes. Nothing should change in Fondoo.
  4. Add Watch Events with webhook.test, turn the scenario on, then ask your agent to run list_webhooks and send_test_event({webhookId}). A bundle should arrive.

Troubleshooting

  • Connection test fails with [401]. The key is wrong or revoked. Paste it again.
  • [403] FORBIDDEN: Missing required scope. The key lacks a scope for that module. Create a new key with the right scopes.
  • Creating the webhook fails with a validation error. If Site ID is empty, Make may send an empty value that Fondoo rejects; this is unverified. Try entering a Site ID. Check also that event types are spelled exactly.
  • No bundles arrive. Run list_webhook_deliveries. Fondoo disables a webhook after three days of failed deliveries; fix it, then use replay_webhook_delivery.
  • status is pending_approval. Nothing happened yet. Approve it in Fondoo.
  • Make shows no output fields. The module interfaces are minimal. Make learns the full structure after the first successful run.

Limits, data and security

  • Rate limits: the Fondoo API allows by default 120 requests per minute per key and 600 per minute per IP, and returns 429 when exceeded. Hosted limits may differ.
  • Webhook delivery: 10-second timeout, no redirects, retries with growing delays (up to 6 hours apart). Deliveries may count toward your plan's event usage.
  • What is stored where: your API key is stored in Make's connection. Fondoo keeps only a hash of it. The webhook secret is encrypted in Fondoo and also saved with the Make webhook.
  • Rotate: create a new key, update the Make connection, then revoke the old key. Disconnect: delete the Make webhook (this removes the Fondoo subscription) and revoke the key.