Skip to content

Repository files navigation

OpnForm Make.com Custom App

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.

How It Works

  1. User searches "OpnForm" in Make's module picker
  2. Creates a connection using their OpnForm API key (Sanctum token)
  3. Selects a workspace and form from dynamic dropdowns
  4. Make auto-registers the dedicated make integration via OpnForm's standard integration API
  5. On each form submission, OpnForm POSTs the Make-specific payload to Make's webhook
  6. When the webhook is deleted, Make auto-unregisters it from OpnForm

Architecture

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.

Structure

├── 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

API Endpoints Used

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

Setup in Make

Docs: developers.make.com/custom-apps-documentation

Option A: Make Web Interface

  1. Log in to Make.com
  2. In the left sidebar, click Custom Apps (click "More" if not visible)
  3. Click + Create app and name it opnform (label: "OpnForm")
  4. Configure the Connection using connection/parameters.json and connection/communication.json
  5. Create a Webhook (dedicated + attached) using webhook/ configs
  6. Create an Instant Trigger module "Watch new submissions" using modules/watchNewSubmissions/ configs
  7. Create RPCs listWorkspaces and listForms using rpcs/ configs
  8. Test end-to-end with a real OpnForm API key
  9. Submit for marketplace review (review takes ~4-6 weeks)

Option B: VS Code Extension

  1. Install the Make Apps Editor VS Code extension
  2. Generate a Make API key with sdk-apps scopes from your Make account
  3. Connect the extension to the existing Make app using the Production origin in makecomapp.json
  4. Run npm test, then deploy the configs to the Testing origin before Production

Related

About

OpnForm Make Integration

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages