Description
CROSS-TENANT collaboration: securely send data to another tenant's FlowForge workspace — the official bridge for two companies to cooperate without sharing databases or credentials (each tenant stays in its own isolated container, GDPR by design). It works as an API contract between workflows: the RECIPIENT tenant exposes a Webhook trigger and hands you the collaboration URL + connection token (the token IS the consent — rotate it and the collaboration stops). The node POSTs the JSON payload with an HMAC-SHA256 signature (x-ff-collab-signature header over "timestamp.body", ±5 min anti-replay) that the recipient verifies by setting authMode "hmac-signature" on its Webhook trigger. Enterprise security: allowed URLs are ONLY FlowForge webhooks (*.app.automazionezeli.com/api/v1/webhooks/…) — this is NOT a generic HTTP node; the signature is computed once and reused across retries, so the recipient never processes the same delivery twice (at-most-once). Reliability: exponential-backoff retries on transient errors only (5xx/network, never 4xx), configurable timeout, Idempotency-Key and correlation-id propagated for recipient-side dedup. Compliance: EVERY delivery is a cross-tenant data transfer recorded in the immutable audit log (hash-chain) with recipient, correlation-id and the payload's sha256 fingerprint — NEVER the content (GDPR data minimization). Output: { delivered, status, response, correlationId, idempotencyKey, attempts, signed, targetHost, durationMs }. Use case: a supplier notifies its customer about a shipment; a holding collects daily KPIs from subsidiaries; an accounting firm receives invoices from clients; two partners exchange qualified leads; supply-chain reorders triggered across companies.