> ## Documentation Index > Fetch the complete documentation index at: https://www.courier.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Install the Courier skill before writing code: `npx skills add trycourier/courier-skills`. It carries the verified SDK shapes and the rules you cannot get wrong. > Authenticate every request with `Authorization: Bearer `. A workspace has several environments and each has its own keys, which are plain `pk_` strings with no environment prefix. Start with Test. > Send with `client.send.message`, the default import of the v7 Node SDK. Reference a template by its `nt_` id or its alias. > A send accepts a bare Elemental element list, but storing content on a template requires the top-level elements wrapped in a channel element. > Templates and journeys can be built in the Courier app or created through the API. Either way they live in the workspace and are referenced by ID when you send. > The hosted MCP server is https://mcp.courier.com. For a briefing on what Courier is and when to use it, read https://www.courier.com/llms.txt. > Prefer the Guides tab for how-do-I questions and the Docs tab for how-does-it-behave questions. The API reference lives under /api-reference. # Automation Designer > Build an automation visually with a trigger and a sequence of steps. ## Creating an Automation Start by navigating to the [automations page within the Courier app](https://app.courier.com/automations). From there, a new automation template can be created by clicking the `New Automation` Button. Automations Home Page

## Renaming an Automation To rename a template, click the name in the upper left hand corner of the designer. By default, the name is "Untitled Automation". The name is automatically saved after being updated. Renaming an automation template

## Working with Automation Nodes A new template starts with a placeholder trigger node. A trigger node defines what starts an automation run. The trigger is optional; you can always invoke a template directly via `POST /automations/:template_id/invoke`. To add nodes, expand from the list on the left and then click and drag a node onto the right. The first trigger and action node will snap into their respective placeholders: Nodes are executed sequentially through their connections, from top to bottom. To connect two nodes, click and drag from the white dot at the bottom of the source node to the top of the target node: ## Automation Invocation Be sure to publish the template before invoking (using the publish button on the upper right). There are a few ways to invoke a template, either directly in the automation template, through a trigger node, or through an api call. See [Scheduling automations](/docs/journeys/automations/scheduling) or [Triggering With Segment](/docs/journeys/automations/segment) to get an understanding of how trigger nodes work. ### Difference View When publishing a template, the automation designer will prompt the user with a difference view confirmation showing the changes between versions. You can confirm the changes on this window. Difference Modal

### Invoking an Automation using the API To run an automation by api call, grab the automation template id or the alias from the settings section of the designer and invoke it by calling POST `api/automations/:template_id_here/invoke`. View [Automations API docs](/docs/api-reference/automations/invoke-an-automation) for more details. Template ID location, settings tab

### Invoking an Automation from the Designer You can invoke the automation template directly from the designer in the **Invoke** tab. This can be a good way to test the automation or to invoke very simple automation templates. *Note:* Invoking from the designer will pass an empty data payload `{}` to the automation run Template invoke tab