Provider-native actions
Call supported services through purpose-built actions instead of maintaining one-off SDK code.
Integration actions
Trigger email, messaging, AI, calendar, and form providers from HTTP requests.
What this helps you do
Trigger email, messaging, AI, calendar, and form providers from HTTP requests.
- Send provider-specific actions from URL workflows
- Use request data and prior action output as variables
- Run side effects asynchronously when speed matters
- Centralize service credentials in connected integrations
Trigger the services your workflow depends on
Integration actions connect endpoint traffic to the services that make work happen. Send messages, create events, call AI providers, submit forms, and trigger provider-specific operations using values from the request and earlier workflow steps.
Workflow variables
Map validated inputs and previous output into emails, messages, events, AI prompts, and forms.
Central credentials
Connected integrations hold auth details, so endpoints can focus on workflow logic.
Related features
Use these features together to build complete endpoint workflows.
Request handling
Validate, authenticate, and rate-limit incoming requests before endpoint actions run.
Auth guards PRO
Protect public endpoints with basic auth, bearer tokens, query keys, or datastore-backed sessions.
Rate limiting PRO
Apply per-endpoint request limits to protect capacity and upstream services.
Signing profiles
Verify webhook signatures from known providers or any HMAC-based source.
Get started in minutes
Everything you need to go from zero to production-ready endpoints.
Create your first endpoint
Sign up, define a URL, and configure auth and validation in a few clicks.
Follow the quickstart
Use the docs to build and test a full endpoint workflow step by step.
Pick a plan when you are ready
Start free, then upgrade for higher limits, advanced features, and team workflows.
Ready to start building?
Get started with Streamnode and build your first endpoint in minutes.