---
title: "Find what a connector can do"
description: "The actions of the app behind a connector, and the input one of them takes."
url: "https://openemail.uk/docs/api/connectors/actions"
area: "API"
category: "Mailbox"
---

# Find what a connector can do

The actions of the app behind a connector, and the input one of them takes.

`GET /connectors/{id}/actions`

**Also documents:** `GET /connectors/{id}/actions/{action}`

## GET /connectors/{id}/actions

The actions of the app behind a connector, and the input one of them takes.

## Example

Needs `connectors:use`. `search` takes a few words, such as `send message`. Left out, the list holds the most used actions. `limit` goes up to 30 and defaults to 12.

**curl**

```
curl "$OE/connectors/cnr_5c1e9a7b3d2f48e6a0b4c7d1/actions?search=send%20message" -H "$AUTH"
curl "$OE/connectors/cnr_5c1e9a7b3d2f48e6a0b4c7d1/actions/SLACK_SEND_MESSAGE" -H "$AUTH"
```

**Response**

```
{
  "object": "list",
  "data": [{
      "object": "connector_action",
      "action": "SLACK_SEND_MESSAGE",
      "name": "Send message",
      "description": "Posts a message to a channel.",
      "kind": "change"
    }]
}
```

> `kind` is `read` when the action only looks something up, and `change` when it creates, updates, sends or deletes something, or when the app does not say.

> A connector whose `access` is `read` lists only the actions that read.

> Reading one action adds `input`, the input it takes as a JSON Schema. Build the `input` of a run from it.

> A connector that is paused, pending or expired answers 409 `connector_not_active`, and a name the app has no action for 404 `connector_action_not_found`.

## Reference

- [`GET /connectors/{id}/actions`](https://openemail.uk/docs/api/reference/connectors#get-connectors-id-actions): full reference
- [`GET /connectors/{id}/actions/{action}`](https://openemail.uk/docs/api/reference/connectors#get-connectors-id-actions-action): full reference