Integrations

Make.com + Meridian

Automate license activation, user provisioning, and subscription management by connecting Meridian to Make.com scenarios via the HTTP module.

1

Create an HTTP Module

In your Make.com scenario, add an HTTP > Make a request module. Configure it with the settings below to call the Meridian license activation endpoint.

HTTP Module Configuration
{
  "url": "https://api.getnimbus.net/v1/license/activate",
  "method": "POST",
  "headers": {
    "Content-Type": "application/json",
    "X-Meridian-Key": "{{YOUR_API_KEY}}"
  },
  "body": {
    "license": "{{licenseKey}}",
    "hwid": "{{hardwareId}}",
    "product": "nimbus"
  }
}
2

Parse the Response

Add a JSON > Parse JSON module after the HTTP request. The Meridian API returns a structured response you can map to downstream modules.

Example Response
{
  "success": true,
  "session": "sess_abc123",
  "expires": "2026-06-15T12:00:00Z",
  "user": {
    "email": "buyer@example.com",
    "plan": "pro"
  }
}
3

Common Scenarios

Webhook → License Activation

Trigger activation when a SellAuth payment completes. Map the webhook payload to the HTTP module body.

Discord DM on Purchase

Chain activation response into a Discord module to DM the buyer their license key and download link.

Google Sheets Logger

Log every activation to a Google Sheet for auditing. Append rows with email, timestamp, and session ID.

Slack Alert on Failure

Route error responses to a Slack channel so your team can investigate failed activations in real time.

API Key Required

All Meridian API requests require an X-Meridian-Key header. Generate your key in the dashboard settings. Keep it secret — store it in Make.com as a scenario variable, never hardcode it in shared blueprints.

Back to DocsZapier Integration