# Call a workflow from your app

> Set up a workflow that your app calls with its own values, then call it from a button in a classic app, from a Vibe app or through the API.

Source: https://tadabase.com/docs/workflows/call-a-workflow-from-an-app  
Status: Verified Nov 17, 2026. Checked against the current product

The **Called from an App** trigger runs a workflow with values your app sends, instead of a record: for example "start a checkout for this plan" or "book this time slot". You declare which values the workflow needs, who may call it and what it sends back.

> **Note:** You set up this trigger in the Tadabase AI builder's Workflows view. The classic workflow editor does not list it under **Trigger Type**, but a classic app can still call these workflows from a button.

## Set up the workflow

1. **Choose the trigger** In the Tadabase AI builder, open **Workflows**, create a workflow and choose **Called from an App** ("When an app calls it with values") in the **Integrations** group. It has no table.
2. **Allow calls** Turn on **Allow apps to call this workflow**. While it is off, nothing can start the workflow.
3. **Declare the inputs** Under **Inputs the app sends**, click **Add input** for each value. Give it a label and a key (lowercase letters, numbers and `_`, starting with a letter), a type (**Text**, **Number**, **Yes / No**, **Date**, **Email** or **JSON**) and an optional default. Tick **Required** if the call must include it, and **Secret (hidden in logs)** for values that must not appear in run logs. Up to 30 inputs.
4. **Choose who may call** Under **Who may call**, turn on **Only signed-in users** and, optionally, tick the roles that may call it. The caller is always taken from the session, never from what the app sends.
5. **Choose the reply** Under **Reply to the app**, choose **Start it and return at once (the app polls the run)**, or **Wait for it and return values** and list the values to send back.
6. **Build, test and switch on** Add your steps. Steps read the inputs as `inputs.<key>`. Save, use **Run test call** to try it with test values, then switch the workflow to **Active**.

Each input is checked before the workflow runs: a missing or wrong value is refused with the reason, and the workflow does not start.

## Call it from a button in a classic app

When you add a **Trigger Workflow** button to a component, workflows Called from an App appear in the workflow list with "(call with values)" after their name. Choose one and a **Pass values** section appears, with one row per input. For each input choose where the value comes from: **Custom value**, **URL parameter**, **Local storage**, **Session storage**, **Logged-in user's field** or **This record's field**.

See [Run a workflow from a button on a page](https://tadabase.com/docs/workflows/triggering-workflows-from-pages-and-buttons) for adding the button.

## Call it from a Vibe app or with the API

- In a Vibe app, call `tada.workflows.call` with the workflow and its inputs.
- From your own code, send `POST /workflows/{workflow id}/call` to your app's API with the values in an `inputs` object.

The workflow must be **Active** and have **Allow apps to call this workflow** turned on; otherwise the call is refused. API calls also need your plan's API access and the app's API switched on ("Allow RLS Permission for API Access" on the Users table's Security API tab). This is the app's own API, the one a Vibe app uses, not the REST API that uses API keys.
