> ## 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

> Create schedules, inbound webhooks, and connected-app triggers that start durable Tasks.

<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>

Automations create Task executions from manual, schedule, connected-app event or inbound-webhook triggers. These inbound deliveries are separate from [outbound task webhooks](/api-reference/webhooks). Definition edits require company write permission plus the Automation’s creator/admin/collaborator management rules. Subscriber management has its own member rules.

## Templates

In **Automations → Templates**, browse workflow templates. The API `area_key` filters are `company`, `product`, `gtm`, `support`, `legal` and `finance`. Templates are available in the company collection and in any Area, including custom Areas.

Choosing a template opens an editable draft. Review the instructions, execution options, and trigger before creating it. Scheduled templates use your browser's timezone. App-event templates require you to select an accessible connected account, an event from its current catalog, and any required configuration. Choosing a template does not create an Automation or start a Task.

## Connected-app events

In **Automations → New automation**, choose **App event**, select an account and event, and complete the event's configuration. Existing Automations can add or edit a connected-app trigger in their detail page. Connect an account in Apps first. If event delivery is unavailable, contact Melso support and use **Retry** once service is restored; your draft stays in the editor.

An integration trigger has `kind: "integration"` and `integration_trigger: {toolkit_slug, connected_account_id, trigger_slug, trigger_config}`. `trigger_config` is an object matching the event's configuration schema. The account must be accessible to the Automation's execution owner in its Area; a collaborator's personal account does not grant that owner access.

Verified events enter the durable delivery queue. A repeated delivery creates at most one invocation for each matching trigger. Its event payload is included in the Task context. Pausing or disabling the Automation stops event dispatch. Trigger subscriptions can be shared upstream, so disabling one Automation preserves other Automations using the same event configuration.

If event setup remains unavailable, contact Melso support before activating the trigger.

## API reference

Request fields, response types and endpoint permissions are defined in the [Automations reference](/api-reference/tags/automations). See [Pagination](/api-reference/pagination) for list conventions, or start with the [API quickstart](/api-reference/quickstart).


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