Your app backend→Workflow Automation→Resend / your app webhook
Your app calls the mod on your server. The mod saves its records in your database and uses your own provider accounts for the features you enable.
Install the package, run its migrations, configure the mod and start its HTTP service as described in README.md. Set MOD_ORIGIN to the service’s origin. Keep its operator token, customer signing secret and provider keys in your server environment. Use the configured HTTPS service origin in production.
Check the service from your private admin backend
Read the saved workflow runs and their progress. This uses the installation’s operator credential for a private administration check. Your backend checks staff permissions before making this request.
Administration request example
Save this as integration-example.mjs and run node --env-file=.env integration-example.mjs. Set HM_API_TOKEN to the private operator token used by the service. These requests do not send email, take payment or call an AI model.
const origin = process.env.MOD_ORIGIN;
const token = process.env.HM_API_TOKEN;
if (!origin || !token) throw new Error('Set MOD_ORIGIN and HM_API_TOKEN');
const response = await fetch(new URL('/api/automation/commands/list_runs', origin), {
method: 'POST', redirect: 'error', credentials: 'omit',
signal: AbortSignal.timeout(10000),
headers: { Authorization: 'Bearer ' + token, 'Content-Type': 'application/json' },
body: JSON.stringify({}),
});
if (!response.ok) throw new Error('Mod request failed: ' + response.status);
console.log(await response.json());
