- REST APIs: Call any HTTP endpoint with custom payloads
- Webhooks: Trigger external services when blockchain events occur
- Database queries: Connect to external data sources
- Cloud functions: Invoke serverless functions on AWS, GCP, or Azure
- External services: Integrate with any service exposing an API
API triggers vs API actions. This page covers API actions — outbound HTTP calls your workflow makes (
Type: post) after it runs. If instead you want to start a workflow with an inbound HTTP request from a Web2 system, you want an API trigger. See API triggers.Configuration
API actions useType: post to make HTTP requests:
Configuration fields
Common integrations
Telegram notifications
You can use Kwala to send messages to Telegram chats or channels. The Telegram notification automation use case shows this integration in detail:Discord webhooks
Kwala supports Discord webhooks that enable sending messages to Discord channels. The following example from the Cryptocurrency deposit alerts use case demonstrates it:Custom webhooks
The following example shows how you can trigger any webhook endpoint with dynamic event data:re.event() syntax:
re.event(0) returns the full transaction receipt which you can parse in your backend. For more details on dynamic data extraction, see Functions.
Using API trigger data in a payload
When the workflow is started by an API trigger, usere.object(\"<field>\") instead of re.event() to pull values from the request body:
re.event() reads positional on-chain event values; re.object() reads named fields from an API trigger body. Use whichever matches what started the run.
Use cases
The following use case demonstrate API integrations in action:Telegram notification automation
Send automated Telegram alerts
Cryptocurrency deposit alerts
Post Discord notifications on deposits
Next steps
API actions
Full API action reference
System overview
Understand the platform architecture
