monday.com trigger

DocRunner can create a packet when something happens on a monday.com board. Each packet template has its own trigger URL that you add to a monday.com webhook or automation.

Requirements

• Your DocRunner account is connected to monday.com.
• The packet template is not archived.

Trigger URL

POST https://app.docrunner.io/api/incoming/:account_slug/:packet_template_slug

Segment	Description
account_slug	Your account's slug.
packet_template_slug	The packet template's slug. The template ID also works.

This URL does not use the X-API-Key header.

Request

monday.com sends the request. DocRunner reads the board and item from the event:

{
  "event": {
    "boardId": 1234567890,
    "pulseId": 9876543210
  }
}

DocRunner then pulls signer and field values from that item, using the column mapping set on the packet template.

When monday.com verifies the URL with a challenge request, DocRunner answers it automatically.

Response

201 Created:

{
  "success": true,
  "packet_id": 123,
  "slug": "abc123",
  "status": "draft"
}

The packet is created as a draft and a link to it is written back to the monday.com item.

Errors

Status	Message	Cause
404	Account not found	The account slug is wrong.
404	Packet template not found	The template slug is wrong.
422	Monday.com not connected	The account has no active monday.com connection.
422	This packet template is archived.
422	Could not build packet from Monday item	The item could not be read or is missing required values.