---
title: "Get the result of an enqueued integration execution"
method: GET
path: "/v1/integrations/executions/{queueId}"
tags: ["Integrations"]
---

# Get the result of an enqueued integration execution

`GET /v1/integrations/executions/{queueId}`

## Request

- Base URL: `https://api.workwing.io`
- URL: `https://api.workwing.io/v1/integrations/executions/{queueId}`
- Auth: HTTP bearer

Returns the status and transformed output of an execution enqueued by `POST /v1/integrations/execute`, using the `queueId` that call returned. Poll this after a 202, or after a 408 from `?wait=true` - the run usually completes regardless, and re-executing repeats the integration's side effects.

`status` is the queue entry's own status (`T_PENDING`, `T_RUNNING`, `T_COMPLETED`, `T_FAILED`). `executionStatus` is the integration's. For an asynchronous integration the queue entry is `T_COMPLETED` as soon as the request is sent, and `executionStatus` stays `T_PENDING` until the third party calls back, then becomes `T_COMPLETED`, `T_FAILED` or `T_EXPIRED` with `output` filled from that callback. A failed run answers 200 with `status: "T_FAILED"`; the provider's error text is recorded server-side and not returned.

Scope: `read:integrations`.

## Path parameters

- `queueId` string, uuid, required

## Response `200`

Default Response

- object
  - `data` object
    - `queueId` string, uuid, required
    - `status` string, required
    - `executionId` string, uuid, nullable, required
    - `executionStatus` string, nullable, required
    - `output` unknown, required
    - `completedAt` string, date-time, nullable, required
  - `meta` object
    - `request_id` string
    - `timestamp` string, date-time

---

[API](https://skmtc.dev/workwing/apis/workwing-api.md) · [All operations](https://skmtc.dev/workwing/apis/workwing-api/llms.txt) · [OpenAPI document](https://skmtc.dev/workwing/apis/workwing-api/revisions/54bb14368a35?raw)