Amplitude

Integrate Amplitude product analytics into your workflows. Track custom events, set user properties, search user records, retrieve event histories, and export raw data — all without leaving your workflow canvas.

Overview

Operations

Configuration

* userId or deviceId — at least one must be provided for amplitude_send_event and amplitude_identify_user.

Outputs

amplitude_send_event

amplitude_identify_user

amplitude_user_search

amplitude_get_user_activity

amplitude_export_events

Example

[Starter] → [Amplitude: Send Event] → [Agent: analyze result]

When a user completes a purchase in your application, a webhook fires the Starter block with order details. The Amplitude block tracks a purchase event using {{AMPLITUDE_API_KEY}} as the API key, with eventType set to purchase, userId set to {{starter.userId}}, and revenue set to {{starter.orderTotal}}. The downstream Agent block then reads {{amplitude.eventsIngested}} to confirm ingestion and generates a follow-up notification.

Tips

• API Key vs. Secret Key: amplitude_send_event and amplitude_identify_user only need the apiKey. The secretKey is additionally required for amplitude_user_search, amplitude_get_user_activity, and amplitude_export_events, which use HTTP Basic Auth (apiKey:secretKey).
• User identification: Always provide either userId or deviceId (or both) when sending events or identifying users — Amplitude will reject requests that have neither.
• Chaining search and activity: Use amplitude_user_search first to resolve a known user ID or device ID into an Amplitude ID, then feed {{amplitudeSearch.matches[0].amplitudeId}} into amplitude_get_user_activity to pull the full event stream.
• Deduplication: Set a unique insertId (e.g., an order ID or idempotency key from upstream blocks) on amplitude_send_event to prevent duplicate events when a workflow retries.