Impulse

View saved version →

---
name: onboarding
description: Set up Impulse and create a first branded event with registration, an attendee landing page, and an automatic confirmation email. Use for first-event setup or resuming unfinished onboarding.
---

# Set up an Impulse event

When creating a new event, you MUST start its pages and emails from the starter/example library and customize those resources. Only create them from scratch if the user explicitly requests it. A request for custom branding or design does not override this requirement.

Help the user get a working event ready to share as fast and easy for the user as possible. Create one registration page, one attendee landing page, and one confirmation email. Match their brand and event style, make sensible design decisions, and keep questions to the facts and preferences you cannot infer. Everything can be edited later. Use your context and everything you know about the user to create an appropriate event without asking too many questions.

## Account and event context

If Impulse is not connected, guide the user through the host's connection flow. They can create an account with verified email or Google there; return to setup after connection.

Use `get_account_context` to confirm the connected account and available capabilities. Check existing events with `list_events` before creating one. Resume an event already identified in this conversation; if several could be the unfinished setup, ask which one. Do not change an unrelated event.

Reuse the user's event description, website, flyer, images, and earlier answers. If context is missing, ask for the event name or purpose and a website or brand reference in one short question. A brand reference is helpful, not required.

Infer colors, typography, tone, layout. Ask only for missing facts that would materially change the event. Do not invent dates, times, venues, ticket prices, agendas, or organizer contact details. Omit unknown details or use “to be announced.” When including a time, establish its timezone from the event's location or the user.

## Choose a design

Read `list_event_presets`. Select the preset that creates registration, an attendee landing page, and one automatic confirmation email. Use its returned ID, page slots, and email names in subsequent calls.

Search `search_page_starters` with `presetId` and `pageType=registration`. Show two to four relevant designs with `show_starter_gallery`. Inspect its image attachments; use the returned `imageIndex` to identify each design. Recommend one direction and let the user choose or ask you to choose. Do not make them select the attendee page and email separately unless they want to.

Choose matching attendee and email starters using `search_page_starters` and `search_email_examples` with the same `presetId`. Use tags and the actual previews to compare them. Read the selected documents with `get_page_starter` and `get_email_example`. Starter IDs from these searches work with `create_event`. `search_page_examples` reads the same released catalog and uses the same IDs; use preset-filtered search to choose a compatible design. Preset event creation copies the catalog assets and binds links between its selected pages and email. Standalone page and email creation copies assets and preserves template links for separate customization.

Choose the confirmation email to match the selected pages' typography, palette and tone. `default-email` is a versatile branded Impulse confirmation; use it when it fits the design. `basic-confirmation` is the minimal option for users who request that style. Inspect the email preview alongside the selected pages before creating the event.

## Create and customize

Call `create_event` with the event name, a suitable URL slug, the preset, and all selected starters. Read the result before continuing.

Customization uses private drafts; publish the finished drafts before reporting the branded event as live, only while onboarding.

Discover the created resources wit

Preview of the first 4,000 characters. Read full instructions →