Activepieces Plugin

Open-source automation alternative to Zapier and Make with bidirectional integration — Gauzy manages Activepieces resources, and the ever-gauzy-piece on Activepieces authenticates back into Gauzy via OAuth 2.0.

Overview

Why Activepieces?

Architecture

The integration is bidirectional:

Diagram source

graph LR
    subgraph Gauzy["Ever Gauzy"]
        SVC["ActivePiecesIntegrationService"]
        CTRL["ActivePiecesController"]
        OAUTH["OAuthAppController"]
        UI["Angular UI Pages"]
    end
    subgraph AP["Activepieces"]
        API["Activepieces API"]
        PIECE["ever-gauzy-piece"]
    end

    SVC -- "API Key (Bearer)" --> API
    PIECE -- "OAuth 2.0 Auth Code" --> OAUTH

Part 1: Gauzy → Activepieces (Plugin Integration)

Setup Flow

1. Obtain API Key — get a key from Activepieces (via sales@activepieces.com or the platform dashboard).
2. Plugin Setup — navigate to /pages/integrations/activepieces and submit the API key via POST /api/integration/activepieces/setup. The backend creates/updates an IntegrationTenant record for the current Gauzy tenant, storing the API key in the settings.
3. Tenant Isolation — all queries include tenantId filtering derived from the authenticated user's JWT. TenantPermissionGuard ensures only authorized users can modify settings.

Connection Management

MCP Server Management

Gauzy manages Model Context Protocol (MCP) servers on the Activepieces platform:

• List servers by project
• Rotate authentication tokens
• Update server tool configurations

Backend API Endpoints

All endpoints are prefixed with /api/integration/activepieces.

Part 2: Activepieces → Gauzy (OAuth App)

OAuth 2.0 Authorization Code Flow

Diagram source

sequenceDiagram
    participant AP as Activepieces Piece
    participant Backend as Gauzy Backend
    participant UI as Gauzy Frontend
    participant User

    AP->>Backend: GET /authorize (client_id, redirect_uri, scope, state)
    Backend->>UI: Redirect to /pages/auth/oauth/authorize
    UI->>User: Show consent screen
    User->>UI: Click "Authorize"
    UI->>Backend: POST /authorize (requires Gauzy JWT)
    Backend->>Backend: Generate HMAC-signed, single-use code (v1.{payload}.{signature})
    Backend->>AP: Redirect with authorization code
    AP->>Backend: POST /token (exchange code for token)
    Backend->>Backend: Validate code, signature, single-use marker
    Backend->>AP: Return JWT access token + expiration

Step-by-step:

1. Authorize Request — GET /authorize with client_id, redirect_uri, scope, state.
2. User Consent — backend validates the request and redirects to /pages/auth/oauth/authorize.
3. Approval — user clicks "Authorize"; frontend calls POST /authorize (requires a Gauzy JWT).
4. Code Generation — backend generates an HMAC-signed, single-use authorization code: v1.{payload}.{signature}.
5. Redirect — user is redirected back to Activepieces with the code.
6. Token Exchange — Activepieces calls POST /token; backend validates code, signature, and single-use marker in cache.
7. Response — returns a Gauzy Access Token (JWT) and expiration.

Security Details

Configuration

Activepieces Plugin (Gauzy → Activepieces)

# Activepieces platform base URL (default: https://cloud.activepieces.com)
ACTIVEPIECES_BASE_URL=https://cloud.activepieces.com

# Activepieces API endpoint (default: https://api.activepieces.com/v1)
GAUZY_ACTIVEPIECES_API_URL=https://api.activepieces.com/v1

# Global API key — fallback if no per-tenant key is configured
GAUZY_ACTIVEPIECES_API_KEY=

OAuth App (Activepieces → Gauzy)

# OAuth client identifier
GAUZY_OAUTH_APP_CLIENT_ID=8012eaea-b166-...

# Client authentication secret
GAUZY_OAUTH_APP_CLIENT_SECRET=5b9d261d96b5...

# HMAC secret for signing authorization codes
GAUZY_OAUTH_APP_CODE_SECRET=TECP70oa2WN...

# Comma-separated redirect URI allowlist
GAUZY_OAUTH_APP_REDIRECT_URIS=https://cloud.activepieces.com/redirect

REDIS_ENABLED=true
REDIS_URL=redis://localhost:6379  # or REDIS_HOST / REDIS_PORT
REDIS_TLS=true                    # for TLS connections (rediss://)

Features

• Self-Hosted Automation — run workflows on your own infrastructure
• Data Privacy — no data leaves your servers
• Unlimited Flows — no per-flow pricing
• Custom Pieces — build Gauzy-specific automation blocks
• Webhooks — trigger flows from Gauzy events

Supported Pieces

Triggers

• Employee created/updated
• Time log recorded
• Task status changed
• Invoice generated

Actions

• Create/update employee
• Log time entry
• Create/update task
• Generate invoice
• Send notification

Related Pages

• Plugins Overview
• Zapier Plugin
• Make Plugin
• Integrations Overview
• Configuration Reference