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

> ## Agent Instructions
> Melso product MCP: https://melso.ai/api/mcp (OAuth; one company per grant). REST: https://melso.ai. Documentation-search MCP: https://docs.melso.ai/mcp. The docs search server does not act on customer accounts.
>
> Use the live tool schema and respect company membership. Ask the person to authorize the exact fiscal document version in the signed-in app. A professional prepares and files included returns after authorization; AI does not file alone. A prepared file or approval receipt is not evidence of filing. Never claim completion from an accepted Task or Run. Keep credentials out of chat and logs. Agents features are internal or by private invitation.

# automations_triggers_create

> Input, output and examples for the automations_triggers_create MCP tool.

<Info>Melso Agents is available only internally or by private invitation. Agents-specific features require existing access. For the autónomo fiscal service, see [Get started](/essentials/quickstart).</Info>

Add a schedule, webhook or connected app trigger to an Automation. Requires company edit access. Webhook credentials are omitted from the result.

**Availability:** Autónomo / Empresa / Agents invitation.

**Catalog:** Advanced (`tools_search`, then `tools_call`).

The live catalog is authoritative: company type, membership, plan, connected apps and execution context can narrow this contract. [Understand access](/mcp/permissions).

## Input

### Agents / Autónomo / Company schema

```json theme={null}
{
  "additionalProperties": false,
  "properties": {
    "automation_id": {
      "description": "Automation UUID.",
      "type": "string"
    },
    "cron_expression": {
      "description": "Required for schedule triggers.",
      "type": "string"
    },
    "idempotency_key": {
      "description": "Optional unique key for this edit; reuse only for retries of the same create.",
      "type": "string"
    },
    "integration_trigger": {
      "additionalProperties": false,
      "description": "Connected app event configuration, required for kind=integration.",
      "properties": {
        "connected_account_id": {
          "type": "string"
        },
        "toolkit_slug": {
          "type": "string"
        },
        "trigger_config": {
          "type": "object"
        },
        "trigger_slug": {
          "type": "string"
        }
      },
      "required": [
        "toolkit_slug",
        "connected_account_id",
        "trigger_slug",
        "trigger_config"
      ],
      "type": "object"
    },
    "kind": {
      "description": "schedule, webhook or integration (connected app event).",
      "enum": [
        "schedule",
        "webhook",
        "integration"
      ],
      "type": "string"
    },
    "label": {
      "description": "Optional trigger label.",
      "type": "string"
    },
    "provider": {
      "description": "Webhook provider: generic or github.",
      "type": "string"
    },
    "timezone": {
      "description": "IANA timezone for schedule triggers.",
      "type": "string"
    }
  },
  "required": [
    "automation_id",
    "kind"
  ],
  "type": "object"
}
```

## Output

The saved Automation or trigger configuration for this edit. A configuration receipt does not mean a scheduled Task has run.

The result uses MCP `content` blocks; JSON payloads are encoded in text and may also appear in `structuredContent`. Check `isError` before reading a success payload. The server does not currently declare an `outputSchema`, so treat additional fields as extensible. [Result handling](/mcp/results).

## Example

Use an OAuth access token issued for this MCP resource (a Run token for Run-only tools). Replace example identifiers with values from your own account. Write actions change data.

First discover `automations_triggers_create` with `tools_search` and confirm that the live schema permits these arguments.

```bash theme={null}
curl --fail-with-body https://melso.ai/api/mcp \
  -H "Authorization: Bearer $MELSO_MCP_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  --data-binary @- <<'JSON'
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "tools_call",
    "arguments": {
      "name": "automations_triggers_create",
      "arguments": {
        "automation_id": "11111111-1111-4111-8111-111111111111",
        "kind": "schedule",
        "cron_expression": "0 9 * * 1",
        "timezone": "Europe/Madrid"
      }
    }
  }
}
JSON
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.