@ever-works/make-plugin

Make.com Workflow Pipeline Plugin - Delegates Work generation to Make.com scenarios and webhooks

Plugin metadata

What does the Make.com plugin do?

This plugin lets Ever Works delegate the work-generation pipeline to Make.com (formerly Integromat), a visual workflow automation platform. Instead of running the built-in pipeline, Ever Works hands each generation request off to a Make.com scenario you design in the Make scenario editor.

You author a scenario with either a Custom Webhook trigger (for direct webhook-mode execution) or any trigger plus a Webhook Response module (for REST-triggered runs), connect whatever modules you need — AI providers, search APIs, HTTP requests, the 1500+ Make app modules — and the plugin invokes that scenario during work generation. The scenario returns structured JSON that Ever Works converts into pipeline outputs (the work draft, items list, categories, tags, brands).

Why use it?

• Connect to Make.com's library of 1500+ app integrations without writing any integration code.
• No-code visual scenario editor with branching, error handling, iterators, and aggregators.
• Two execution modes — REST API scenario runs (with polling) or direct webhook URL invocation — pick whichever matches your scenario design.
• Swap in custom logic, change AI providers, or add data-enrichment steps without touching Ever Works code.
• Reuse existing Make scenarios, connections, and data stores you already maintain for other automations.

How it works in Ever Works

When this plugin is selected as the active pipeline, the platform sends each generation request to Make either via a scenario REST run (POST /scenarios/{id}/run with polling on /executions/{id} when needed) or directly to a webhook URL. The scenario runs in Make — optionally calling AI providers, search APIs, scrapers, etc. — and returns a structured JSON response, either inline in the run response (when using responsive: true synchronous runs with a Webhook Response module) or via the webhook reply. The plugin parses that response back into Ever Works pipeline outputs (the work draft, items list, categories, tags). The required output schema is documented in the Ever Works docs.

Getting started

1. Sign up at make.com and note your zone (e.g. us2, eu1).
2. Create a new scenario with either a Custom Webhook trigger or a Webhook Response module that emits the JSON shape Ever Works expects.
3. Generate an API token in your Make profile (with the scopes required for scenarios and hooks) and copy your scenario ID — and the webhook URL if you plan to use webhook-mode execution.
4. Open the Make.com plugin settings in Ever Works, paste the API key, set the zone-specific base URL (e.g. https://us2.make.com/api/v2), and provide the default scenario ID, hook ID, or webhook URL. Save.
5. Trigger a run from the Generate flow.

Settings

• apiKey (secret) — Make.com API token. Required.
• baseUrl — Zone-specific API base URL (e.g. https://us2.make.com/api/v2).
• teamId — Optional team ID used to scope scenario and hook queries.
• organizationId — Optional organization ID used when no team ID is provided.
• defaultScenarioId — Default scenario invoked when the generator form does not specify one.
• defaultHookId — Optional default hook (webhook) ID to ping during the pipeline.
• defaultWebhookUrl — Default webhook URL for webhook-mode execution.

The generator form additionally exposes per-run options including execution mode (scenario vs. webhook), scenario/hook/webhook overrides, target item count, scenario timeout, repository access pass-through, and custom scenario parameters.

Troubleshooting

Local development

This plugin ships built-in with the Ever Works platform. To work on it locally from the monorepo root:

pnpm install
pnpm --filter @ever-works/make-plugin build
pnpm --filter @ever-works/make-plugin test

Documentation

• Ever Works documentation
• Ever Works repository
• Plugin system
• Make.com homepage
• Make.com API documentation

License

AGPL-3.0