Make App

Use the Allowly Make app to create authorizations from Make scenarios, then check sensitive modules before the scenario continues.

make-allowly-app

Status

The Make Custom App configuration is planned as the public repository Allowly-AI/make-allowly-app.

Connection

Configure an Allowly connection with:

• API Key
• API URL, defaulting to https://api.allowly.ai

The connection test calls GET /v1/agent-scope-bundles?limit=1. Use a key that can list agent scope bundles and create authorizations.

Modules

Create Authorization

Create an Allowly authorization from a user and an agent scope bundle. Store the returned authorizationId in the scenario or your app data, then reuse it for checks.

Required fields:

• Bundle
• User Identifier
• User ID, or User Email plus User ID Pepper when masking email locally

The Bundle field is loaded by an RPC that calls GET /v1/agent-scope-bundles.

Check Authorization

Check a stored authorization before a Make module takes action. The module returns the Allowly decision object so the scenario can branch on allow, deny, confirm, or escalate.

Required fields:

• Authorization ID
• Scopes

Optional fields include resource, session ID, estimated cost micros, workflow user ID, workflow agent ID, and additional context. Those context fields are copied into the Allowly check context and receipt; they do not replace the authorization.

Privacy-safe user IDs

For email-based scenarios, prefer masking email locally before sending a user_id to Allowly. The app derives an email_hmac:v1:<digest> value with a stable app-held pepper, so the raw email is not sent to Allowly.

See PII-safe identifiers for the identifier format.