The Internal API Executor calls UnifyApps' own internal platform API endpoints from within an automation. It is distinct from Custom HTTP, which calls external third-party APIs. This node is an admin-level capability designed for platform-administration automations.

Overview

Use Internal API Executor when an automation needs to interact with UnifyApps' own internal platform APIs — for example, to perform administrative actions that have no dedicated built-in node. It supports the standard HTTP structure: method, headers, query parameters, path parameters, and request body.

Screenshot_2026-08-29_at_10.21.17_PM_1.png

Note: For calling external APIs and third-party services, use the Custom HTTP node instead. Internal API Executor is intended only for calls to UnifyApps internal endpoints.

Permissions and Audit Logging

The Internal API Executor is an admin-only capability:

The user running the automation must hold the internal-API execution permission, or the call fails.
Every call is audit-logged — this cannot be disabled. All executions are recorded in the platform's audit trail.

Treat this node as a privileged tool. Keep its use intentional, limited to legitimate platform-administration needs, and ensure your team is aware that all executions are logged.

Notes

The Internal API Executor works best when you follow these practices:

Internal API Executor details

If you do not have the internal-API execution permission, calls from this node will fail at runtime — request the permission from your workspace administrator before building automations that rely on it.
The audit log entry for each call includes the endpoint, parameters, and the identity of the automation that executed it.
For any external API call, always use Custom HTTP rather than this node.

A well-configured Internal API Executor reduces errors and keeps automations maintainable.