Use AI to prepare an event and its tickets

Try: “Help create our event and tickets. Show me the plan before creating anything.”

Required facts

Provide the page, name, date, start and end, venue, visibility, capacity and registration mode. For each ticket: name, price, quantity, eligibility and sale window. Clarify missing facts rather than inventing them. Dates need a year and timezone, normally Europe/Copenhagen with the correct summer or winter offset.

Workflow for the AI assistant

1. Read pages with hap_read and access pages list. Check existing events to avoid duplicates.
2. Look up events create and tickets types create with hap_help and its command field. Use only flags offered by the current connection.
3. Present a combined plan covering dates, visibility, prices, eligibility and capacity. A name such as “member ticket” does not restrict access.
4. Preview with hap_run and dry_run: true. A command_only preview does not validate business rules or create anything.
5. After approval, execute the agreed change with dry_run: false. Use the returned event ID for the tickets and verify after each step.

Verification and stopping points

Check amount units in help: for prices in øre, 150 kr means 15000. Always show the currency.

Reread with events get and tickets types list. Report actual status and remaining steps. Do not call the event a saved draft unless the response establishes that; creation, visibility and publication are separate checks.

If a response is lost, locate the created event before retrying. Do not share the link or send invitations without a corresponding instruction.

Test before sharing. Standard ticket setup.