> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Monday.com

> Update Monday.com boards automatically from DialNexa calls - items created, statuses updated, and team members notified based on what happened on the call.

Monday.com is where many operations and project teams manage their work - lead tracking, project boards, customer onboarding checklists, service request queues. When DialNexa makes calls related to any workflow you manage in Monday, it can update the right board item automatically - status changed, column updated, note added, and the right person notified.

<Note>
  Monday.com is a versatile destination for call data - whether you use it as a lightweight CRM, an operations tracker, or a project management tool. DialNexa writes outcomes to whichever board or workflow makes sense for your team.
</Note>

## What this integration does

DialNexa connects to Monday.com through the Monday GraphQL API. After a call, DialNexa can:

* **Update an item's status column** based on call outcome (e.g., "Called," "Interested," "Not Now," "Booked")
* **Update other columns** - date columns, text columns, numbers, dropdowns, and people columns
* **Create a new item** in a board when the call produces a new lead or request
* **Add an update (comment)** to the item with the call summary and context
* **Notify team members** assigned to the item via Monday's notification system
* **Search for existing items** by phone or email to avoid duplicates

## When to use DialNexa with Monday.com

**Sales and lead tracking** - your team tracks prospects in a Monday sales CRM board. DialNexa calls the list, qualifies leads, and updates each board item with the call outcome - changing the status column from "To Call" to "Interested" or "Not Interested," with notes added.

**Customer onboarding** - for teams managing onboarding projects in Monday, DialNexa makes the check-in calls and marks each onboarding item as complete, flagged, or needing follow-up directly on the project board.

**Service requests and operations** - field service, facilities, or operations teams that manage jobs in Monday can use DialNexa to call customers for appointment confirmation and update the job status in Monday based on the call outcome.

**Partnership and agency outreach** - business development teams tracking outreach in a Monday board can use DialNexa to run the calls and automatically update pipeline status after each conversation.

**Event and campaign management** - event coordinators who track registrants or campaign contacts in Monday boards can use DialNexa to call them and update their Monday items with call outcomes.

## What DialNexa writes to Monday.com

<CardGroup cols={2}>
  <Card title="Status column updates" icon="circle">
    Changes the status of the right Monday item based on call outcome - the visual traffic light that tells your team what state each item is in.
  </Card>

  <Card title="Column updates" icon="table">
    Fills in date columns (last called, next follow-up), text columns (notes, contact name), people columns (assigned rep), and number columns (call count, score).
  </Card>

  <Card title="Item creation" icon="plus-circle">
    Creates a new Monday item when a call generates a new lead, request, or case not already tracked on the board.
  </Card>

  <Card title="Updates (comments)" icon="message-circle">
    Adds a structured comment to the Monday item with the call summary, outcome, and what happens next - visible to everyone on the board.
  </Card>
</CardGroup>

## Setting up the integration

In your DialNexa agent workflow, add a Monday.com action after the call. You'll configure:

1. **Monday.com API token** - from your Monday account settings (set up once in DialNexa integrations)
2. **Board selection** - which Monday board to write to
3. **Action** - update item, create item, add update, or search items
4. **Item matching** - how DialNexa finds the right item (by phone, email, or a custom ID column)
5. **Column mappings** - which Monday columns receive which DialNexa call variables
6. **Status mapping** - which call outcomes update the status column to which label

## Workflow ideas

<AccordionGroup>
  <Accordion title="Sales outreach: run the list, update the board">
    Your team builds a prospect list in a Monday sales CRM board. DialNexa calls every item where Status = "To Call." After each call, the status updates - "Interested," "Call Back," "Not Interested," or "No Answer." A comment is added with the call notes. By end of day, the board reflects the exact state of every prospect without a single manual update.
  </Accordion>

  <Accordion title="Onboarding calls: mark milestones complete automatically">
    Your customer success team manages onboarding projects in Monday - each row is a customer, each column is an onboarding milestone. When DialNexa makes the Week 1 check-in call, it marks the "Week 1 Call" column as Done, adds notes from the call, and assigns any blockers to the CSM for follow-up.
  </Accordion>

  <Accordion title="Service confirmation: update job status before dispatch">
    Your field service team manages jobs in a Monday board. The night before, DialNexa calls every customer to confirm their appointment. Confirmed jobs get Status = "Confirmed." Reschedules get a new date in the date column and Status = "Rescheduled." Cancellations get Status = "Cancelled." The dispatcher sees an accurate board every morning.
  </Accordion>

  <Accordion title="Event attendance: update registrant records from calls">
    Pre-event, DialNexa calls all registrants to confirm attendance. Each registrant is a Monday item. The call updates the "Attendance Status" column - Attending, Not Attending, or Needs Follow-Up. Your events team sees real-time attendance confirmation without managing a spreadsheet.
  </Accordion>
</AccordionGroup>

## Pairing Monday.com with other integrations

* **Monday.com + Slack** - when a Monday item status changes from a call (e.g., new hot lead, service cancellation), Slack notifies the relevant team member with the Monday item link
* **Monday.com + Gmail** - after updating a Monday item, trigger a Gmail follow-up email to the caller with the next step details
* **Monday.com + Google Calendar** - when an appointment is confirmed via call, update the Monday item and create the Google Calendar event simultaneously
* **Monday.com + HubSpot** - for teams that use both, write the call outcome to the Monday board for operations visibility and to HubSpot for CRM tracking

## Common questions

<AccordionGroup>
  <Accordion title="How does DialNexa find the right Monday item to update?">
    DialNexa searches the board for an item that matches the caller's phone number or email - stored in a designated column in your Monday board. If no match is found, it can create a new item or route to review. If the call was sourced from a Monday list, DialNexa carries the item ID directly.
  </Accordion>

  <Accordion title="Can DialNexa read from Monday to build a call list?">
    Yes. DialNexa can pull items from a Monday board where the status is "To Call" or any other filter, and use that as the call list for an outbound campaign. Each item's columns become the call data the agent uses.
  </Accordion>

  <Accordion title="Which Monday column types does DialNexa support?">
    DialNexa supports the most common Monday column types: status, text, long text, date, number, dropdown, people, and checkbox. Complex column types like formula, mirror, or dependency columns are read-only.
  </Accordion>

  <Accordion title="Can DialNexa notify the Monday item's assigned person?">
    Yes, indirectly - by updating a people column and adding an update (comment) to the item, Monday's native notification system will notify the assigned person that the item was updated.
  </Accordion>

  <Accordion title="Does this work with Monday subitems?">
    DialNexa can create and update subitems using the Monday API. This is useful when each call is a subitem under a parent deal or project item.
  </Accordion>
</AccordionGroup>