Configuration files for the OpnForm custom app on Make.com (formerly Integromat).
This app provides a "Watch new submissions" instant trigger so Make users can automate workflows whenever a form receives a submission, plus the required "Make an API call" universal module for authorized requests to the OpnForm API.
- User searches "OpnForm" in Make's module picker
- Creates a connection using their OpnForm API key (Sanctum token)
- Selects a workspace and form from dynamic dropdowns
- Make auto-registers the dedicated
makeintegration via OpnForm's standard integration API - On each form submission, OpnForm POSTs the Make-specific payload to Make's webhook
- When the webhook is deleted, Make auto-unregisters it from OpnForm
This integration follows the same lightweight pattern as OpnForm's Activepieces integration. It uses OpnForm's existing /open/* API -- no dedicated Make endpoints are needed. The existing API accepts integration_id: "make" through OpnForm's integration registry and dispatches submissions through MakeIntegration, which removes the deprecated generic submission field and exposes form_id, form_title, form_slug, submission_id, optional edit_link, and data.
├── base.iml.json # Shared API base URL, authorization, errors, and log sanitization
├── connection/
│ ├── parameters.json # Connection dialog fields (API key)
│ └── communication.json # Auth validation (GET /open/workspaces)
├── webhook/
│ ├── parameters.json # Webhook parameters (form selection)
│ ├── communication.json # Convert the incoming request body to a Make bundle
│ ├── attach.json # Register webhook (POST /open/forms/{id}/integrations)
│ └── detach.json # Unregister webhook (DELETE /open/forms/{id}/integrations/{id})
├── modules/
│ ├── watchNewSubmissions/
│ │ ├── communication.json # Empty: the paired webhook already produces the bundle
│ │ ├── parameters.json # Empty: form/workspace selectors belong to the webhook
│ │ └── expect.json # Empty: form/workspace selectors belong to the webhook
│ └── makeAnApiCall/ # Authorized REST universal module using relative API paths
└── rpcs/
├── listWorkspaces.json # Dynamic dropdown (GET /open/workspaces)
└── listForms.json # Dynamic dropdown (GET /open/workspaces/{id}/forms) with bounded pagination
All endpoints are part of OpnForm's existing API, authenticated via Bearer token (Sanctum):
| Endpoint | Method | Purpose |
|---|---|---|
/open/workspaces |
GET | Validate API key + list workspaces |
/open/workspaces/{id}/forms |
GET | List forms (paginated, up to 100/page and 300 results per picker load) |
/open/forms/{id}/integrations |
POST | Create Make integration (attach webhook) |
/open/forms/{id}/integrations/{integrationId} |
DELETE | Remove integration (detach webhook) |
| Any relative path selected by the user | Any supported REST method | Universal authorized API call |
Docs: developers.make.com/custom-apps-documentation
- Log in to Make.com
- In the left sidebar, click Custom Apps (click "More" if not visible)
- Click + Create app and name it
opnform(label: "OpnForm") - Configure the Connection using
connection/parameters.jsonandconnection/communication.json - Create a Webhook (dedicated + attached) using
webhook/configs - Create an Instant Trigger module "Watch new submissions" using
modules/watchNewSubmissions/configs - Create RPCs
listWorkspacesandlistFormsusingrpcs/configs - Test end-to-end with a real OpnForm API key
- Submit for marketplace review (review takes ~4-6 weeks)
- Install the Make Apps Editor VS Code extension
- Generate a Make API key with
sdk-appsscopes from your Make account - Connect the extension to the existing Make app using the
Productionorigin inmakecomapp.json - Run
npm test, then deploy the configs to the Testing origin before Production
- OpnForm main repository -- contains the integration handler
- OpnForm documentation