Appearance
Plugin/Integration actions ​
Some plugins and backend integrations add dedicated actions you can use in workflows. These appear in the action picker once the plugin/integration is installed and configured.
Typical flow:
- Add a plugin/integration to your project
- Open a workflow, click
Add an action - Search for the action by name or expand the plugin’s category
Examples by plugin/integration ​
Resend integration (backend) ​
- Action: Send Email
- Use to send transactional emails from APIs.
- Docs: Resend integration →
REST API plugin ​
- Action: REST API Request
- Use to call any HTTP API directly from workflows (supports streaming).
- Docs: REST API data source →
WeWeb Email plugin ​
- Action: Send an email
- Simple email sending from interface workflows (separate from Resend backend).
- Docs: WeWeb Email →
PWA plugin ​
- Actions: Install PWA, Get user's location, Share, Vibrate, Show notification
- Mobile/web capabilities exposed to workflows, plus a
PWAsection in the variables explorer. - Docs: PWA →
Segment plugin ​
- Actions: Track, Identify
- Send analytics events and identify users.
- Docs: Segment →
Sound plugin ​
- Actions: Load sound, Play, Pause, Stop, Unload
- Control audio playback in the app.
- Docs: Sound →
Stripe plugin ​
- Common action: Retrieve payment intent (then bind to UI/variables, confirm via Stripe elements)
- Docs: Stripe →
Xano request (extension) ​
- Action: Xano request
- Convenience wrapper to call Xano endpoints.
- Docs: Xano request action →
Authentication Systems (WeWeb Auth, Supabase, Auth0, Custom Auth, OpenID Connect) ​
- Actions vary by system and include things like sign up, sign in, magic links, one-time passwords, and sign out.
- Docs:
Tips ​
- Install first: actions only appear after the plugin/integration is added.
- Test with safe data: many integrations have environment‑specific limits (e.g., Resend requires verified senders/domains for real recipients).
- Prefer variables: bind results to variables so subsequent actions can use outputs reliably.

