Record the outcome of a monday.com action
Called by the customer's own app server with an Authorization JWT signed with the monday app's client secret that names the installer (accountId, userId)...
POST/api/v1/monday.com/actions/orgId
- Sign-in
- None at the router: the operation is public, or checks its own proof (a signature, a token in the body, a signed link).
- Rate limit
- Up to 500 requests every 3 seconds per IP address; up to 1,000 requests a minute per API key (some requests are not counted); up to 600 requests a minute per mondayActionLimiterKey.
Called by the customer's own app server with an Authorization JWT signed with the monday app's client secret that names the installer (accountId, userId) and expires within five minutes; anything else answers 401. Creates or updates the action log entry for actionLogId, and answers 403 when the body names a different installer than the signature.
Request
Path parameters
| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
orgId | string | Yes | - | - |
Send the body as application/json.
Body
| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
actionLogId | string | Yes | - | - |
actionTimestamp | string | Yes | - | - |
actionType | string | Yes | - | - |
accountId | number | Yes | - | - |
userId | number | Yes | - | - |
boardId | number | Yes | - | - |
itemId | number | Yes | - | - |
recipeId | number | Yes | - | - |
integrationId | number | Yes | - | - |
status | string | Yes | one of "failed", "pending", "success" | - |
error | string | No | - | - |
result | object | No | - | - |
Example request
Replace each YOUR_... value with your own.
curl -X POST "https://api.console.buildbase.app/api/v1/monday.com/actions/YOUR_ORG_ID" \
-H "Content-Type: application/json" \
-d '{
"actionLogId": "YOUR_ACTION_LOG_ID",
"actionTimestamp": "string",
"actionType": "string",
"accountId": 1,
"userId": 1,
"boardId": 1,
"itemId": 1,
"recipeId": 1,
"integrationId": 1,
"status": "failed"
}'const response = await fetch(
'https://api.console.buildbase.app/api/v1/monday.com/actions/YOUR_ORG_ID',
{
method: 'POST',
headers: {
'Content-Type': 'application/json',
},
body: JSON.stringify({
actionLogId: 'YOUR_ACTION_LOG_ID',
actionTimestamp: 'string',
actionType: 'string',
accountId: 1,
userId: 1,
boardId: 1,
itemId: 1,
recipeId: 1,
integrationId: 1,
status: 'failed',
}),
}
);
if (!response.ok) {
throw new Error(`${response.status}: ${await response.text()}`);
}
const data = await response.json();import requests
response = requests.post(
"https://api.console.buildbase.app/api/v1/monday.com/actions/YOUR_ORG_ID",
json={
"actionLogId": "YOUR_ACTION_LOG_ID",
"actionTimestamp": "string",
"actionType": "string",
"accountId": 1,
"userId": 1,
"boardId": 1,
"itemId": 1,
"recipeId": 1,
"integrationId": 1,
"status": "failed",
},
timeout=30,
)
response.raise_for_status()
data = response.json()Responses
200 OK
OK
{
"data": {
"_id": "000000000000000000000001",
"accountId": 634771,
"actionLogId": "e2e-action-1767225600000",
"actionTimestamp": "2026-01-01T00:00:00.000Z",
"actionType": "create_item",
"boardId": 11,
"createdAt": "2026-01-01T00:00:00.000Z",
"deleted": false,
"error": "",
"id": "000000000000000000000001",
"integrationId": 33,
"itemId": 44,
"recipeId": 22,
"result": {},
"status": "success",
"updatedAt": "2026-01-01T00:00:00.000Z",
"userId": 634771
},
"success": true
}Any other status
Any other answer the handler sends itself (its own refusals). Not described yet.
Errors
Each refusal, what it means, and what to do. The request changed nothing.
400 Bad Request
What it means: The request failed a validate() schema, or an id in the path is not a valid id. path names the field.
What to do: Fix the field the body names in path (or read message) and send the request again. Nothing was changed.
{
"error": true,
"success": false,
"path": "string",
"message": "string"
}404 Not Found
What it means: An id in the path names nothing in this org.
What to do: Check the ids in the path: one of them names nothing in this organization.
{
"success": false,
"message": "string"
}429 Too Many Requests
What it means: A rate limit in x-rateLimit was reached. retryAfter and the Retry-After header say how many seconds until the window resets.
What to do: Wait the number of seconds in the Retry-After header (also retryAfter in the body), then retry. Slow down repeated calls.
{
"success": false,
"message": "string",
"reason": "rate_limited",
"retryAfter": 1
}Related
- monday.com guide: how this part of BuildBase works
- All monday.com operations
- API reference: every operation, by tag
- Sign-in and credentials for the HTTP API
- How the HTTP API reports errors
- Make your first call
- Error codes: every
codethe API returns - OpenAPI: operation
mondayCom.actions.createin public-v1.json