Custom API Action
Make a custom, authenticated HTTP call to the monday.com API.
In the 2023-10 version of the monday.com API, the response values for identifiers changed type from number to string. Refer to the monday.com API documentation.
Input
Field | Definition | Type | Required |
---|---|---|---|
Request |
|||
Headers |
Specify any headers required in addition to authorization or content-type, as the connector already handles those. For example: {"Content-type":"application/json"} |
Object |
FALSE |
Body |
Specify a request body in the GraphQL language to fetch or modify specific data. The string must begin with query or mutation. For example:
|
Text |
TRUE |
Variables |
Specify any dynamic arguments used in the query or mutation instructions. Add your variable values without a leading $ sign. |
Object |
FALSE |
Example
Query a user through a dynamic user ID value:
- Headers
- {}
- Query
- query($my_user_id: Int!) { users(ids: [$my_user_id]) { id name }}
- Variables
- { "my_user_id": 11111111 }
Output
Field | Definition | Type |
---|---|---|
Response |
||
Status Code |
Result of the operation. The connector returns an HTTP status code that indicates whether the action taken by the card succeeded or failed. For example:
For a full list of possible status codes, see HTTP status codes. |
Number |
Headers |
Detailed context for the status code, unrelated to the output body. Response headers depend on your selected HTTP request option. Not all headers are response headers. This is similar to {"Content-type":"application/json"}. |
Object |
Body |
Data returned from your selected HTTP request. For example, the data from a GET request. |
Object |