Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mossdesk.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

MossDesk is designed to be agent-operable — every action available in the dashboard can be performed via CLI or API. This makes MossDesk a natural fit for AI coding agents that can run shell commands or make HTTP requests.

​
How it works

AI agents interact with MossDesk through:
  1. CLI commands — Agents execute moss commands in a terminal, using --json for structured output
  2. API calls — Agents make HTTP requests to the REST API with an X-API-Key header
  3. Exit codes — Agents can branch on success/failure using standardized exit codes

​
Compatible agents

AgentInterfaceSetup
Claude CodeCLIAdd instructions to CLAUDE.md
CursorCLI or APIConfigure in .cursorrules
CodexCLI or APIAdd to system prompt
Custom agentsAPIUse any HTTP client

​
Setting up Claude Code

Add the following to your project’s CLAUDE.md: 
## CRM Access

This project uses MossDesk. The CLI is available as `moss`.

- Use `moss --json` for all commands to get structured output
- API key is configured in `~/.moss/config.json`
- Current workspace: <your-workspace-id>

### Common tasks
- Check pipeline: `moss pipeline show --json`
- List today's follow-ups: `moss followup today --json`
- Log an interaction: `moss interaction log --contact-id <id> --type note --content "..."`
- Search contacts: `moss search --q "query" --json`

​
Structured output with --json

Every CLI command supports the --json flag, which outputs data in a consistent JSON envelope: 
# Single resource
moss contact show <id> --json

{
  "data": {
    "id": "cnt_abc123",
    "name": "Jane Smith",
    "email": "jane@acme.com"
  }
}

# List
moss contact list --json

{
  "data": [
    { "id": "cnt_abc123", "name": "Jane Smith" },
    { "id": "cnt_def456", "name": "Bob Chen" }
  ],
  "meta": {
    "page": 1,
    "per_page": 25,
    "total": 2,
    "total_pages": 1
  }
}

​
Exit codes for control flow

Agents can use exit codes to handle errors programmatically:
CodeMeaningAgent action
0SuccessProceed
1General errorRetry or report
2Validation errorFix input and retry
3Authentication errorRe-authenticate
4Not foundHandle missing resource
5Rate limitedBack off and retry
Example in a script: 
if moss contact show "$CONTACT_ID" --json > /dev/null 2>&1; then
  echo "Contact exists"
else
  exit_code=$?
  if [ $exit_code -eq 4 ]; then
    echo "Contact not found, creating..."
    moss contact create --name "$NAME" --email "$EMAIL" --json
  fi
fi

​
Example agent flows

​
Daily CRM review

# Check overdue follow-ups
moss followup overdue --json | jq '.data[] | "\(.title) — due \(.due_date)"'

# Check today's follow-ups
moss followup today --json | jq '.data[] | "\(.title) — \(.contact_name)"'

# Get pipeline summary
moss pipeline show --json | jq '.data'

​
Post-meeting logging

# Log the interaction
moss interaction log \
  --contact-id cnt_abc123 \
  --type meeting \
  --content "Discussed Q2 roadmap. They want SSO before signing." \
  --json

# Create a follow-up
moss followup create \
  --title "Send SSO timeline to Jane" \
  --contact-id cnt_abc123 \
  --due-date 2026-02-10 \
  --priority high \
  --json

# Record commitment
moss commitment create \
  --title "Deliver SSO implementation timeline" \
  --contact-id cnt_abc123 \
  --due-date 2026-02-10 \
  --json

​
Pipeline management

# Move deal to next stage
moss deal move <deal-id> --stage proposal --json

# Bulk move stale leads
moss deal bulk-move --from-stage lead --to-stage lost \
  --older-than 90d --json

​
Best practices

  1. Always use --json — Table output is for humans; JSON output is for agents
  2. Check exit codes — Don’t assume success; handle errors gracefully
  3. Use --request-id — Pass a unique request ID for tracing and debugging
  4. Use --idempotency-key — Prevent duplicate creates when retrying
  5. Scope API keys — Create a dedicated API key with minimum required scopes for each agent