Appearance
Shortcut
undefined
| Detail | Value |
|---|---|
| Category | Project Management |
| Base URL | https://api.app.shortcut.com/api/v3 |
| Authentication | API Key |
| Endpoints | 7 |
| Connector key | shortcut |
Using Shortcut in a workflow
- Go to Connections and click New Connection.
- Pick Shortcut from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | Create Story |
GET | Search Stories |
GET | List Epics |
GET | List Iterations |
GET | List Workflows |
GET | List Members |
GET | List Labels |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Create Story
| Detail | Value |
|---|---|
| Operation ID | create_story_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Shortcut connection from the Connection dropdown.
- In the Operation dropdown, select
create_story_0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Shortcut API reference.
GET
Search Stories
| Detail | Value |
|---|---|
| Operation ID | search_stories_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Shortcut connection from the Connection dropdown.
- In the Operation dropdown, select
search_stories_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Shortcut API reference.
GET
List Epics
| Detail | Value |
|---|---|
| Operation ID | list_epics_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Shortcut connection from the Connection dropdown.
- In the Operation dropdown, select
list_epics_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Shortcut API reference.
GET
List Iterations
| Detail | Value |
|---|---|
| Operation ID | list_iterations_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Shortcut connection from the Connection dropdown.
- In the Operation dropdown, select
list_iterations_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Shortcut API reference.
GET
List Workflows
| Detail | Value |
|---|---|
| Operation ID | list_workflows_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Shortcut connection from the Connection dropdown.
- In the Operation dropdown, select
list_workflows_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Shortcut API reference.
GET
List Members
| Detail | Value |
|---|---|
| Operation ID | list_members_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Shortcut connection from the Connection dropdown.
- In the Operation dropdown, select
list_members_5. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Shortcut API reference.
GET
List Labels
| Detail | Value |
|---|---|
| Operation ID | list_labels_6 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Shortcut connection from the Connection dropdown.
- In the Operation dropdown, select
list_labels_6. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Shortcut API reference.