> ## 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. # Sync events between RudderStack and Courier > Route RudderStack events into Courier journeys, and stream message events back. export const Doc = ({href, children, name, bare}) => { const label = children || name || href; if (bare) { return {label}; } return {label} DOC ; }; RudderStack events flow into Courier, and Courier events flow back out. Outbound sends need your RudderStack write key and data plane URL. ## RudderStack to Courier RudderStack supports Courier as a destination. Configure it inside RudderStack, connect one or more sources, and events start flowing into Courier. Inbound events appear on the RudderStack integration page in Courier Studio. Map them there to trigger notification workflows. An `identify` event can trigger an automation that welcomes a new user. **Supported RudderStack events:** * Group * Identify * Track ### Configuration Go to RudderStack destination and search for Courier. Search Courier Destination Connect one or more sources Connect Sources to Courier Destination Add Courier API Key Add Courier API Key ### Event trigger Trigger events through the sources you connected, or by calling RudderStack endpoints directly. The Courier destination supports `group`, `identify` and `track` events. They appear on the RudderStack integration page in Courier Studio. See the [RudderStack Node SDK documentation](https://www.rudderstack.com/docs/sources/event-streams/sdks/rudderstack-node-sdk/#sending-events) for sending events to your RudderStack instance. Courier Inbound from RudderStack ### Supported events #### Identify Identify events create or update a Courier user profile. The `userId` becomes the user identifier. The `traits` map to user profile attributes. #### Track Track events can trigger an automation or supply an inline automations payload. The `properties` in the payload map to Courier. #### Group Group events can create an account or trigger an automation. The `groupId` becomes the Account ID. The `userId`, or `anonymousId` if `userId` is absent, becomes the User Identifier. ### Event mapping Map a received event to an existing automation, or create a new automation with the event as its trigger. Click the plus (+) icon under link automations, then pick an existing automation template or create one. Scope properties by the `courier.automation` object. To map userId to refs, send this to RudderStack: ```json Rudderstack Courier Automation Property Example theme={null} { "event": "user-checkout", "type": "track", "properties": { "courier": { "automation": { "data": { "userId": "user_123" } } } } } ``` Mapped automation would look like this: RudderStack Mapped Automation V2 Learn more about Journeys > *** ## Courier to RudderStack Courier generates events during workflow execution (for instance, a "message sent" event when a message is delivered). These events can be sent outbound to RudderStack, which can further unlock other use cases and wire up other destinations inside RudderStack. ### Configuration Add a source in RudderStack that will receive events from Courier (for example, a Node.js source). Once the source is created, copy the write key and data plane URL to the Courier RudderStack integration page. RudderStack Source Config Courier RudderStack Source Config ### Event sourcing Courier will start sending generated events (like Message Sent) to your RudderStack instance. These should show up on your RudderStack source page. Courier to RudderStack Events *** ## Example use cases * User sync from RudderStack to Courier * Welcoming new users based on sign-up tracking * Nudging users to upgrade to a paid tier based on usage tracking