Create an agenda with an agent

A practical workflow for turning unstructured event material into speakers, sessions and their connections.

Use an authorized agent to create an agenda and connect speakers through the Core API. Start with your existing notes or documents, review the proposed plan, and verify a small sample before importing the rest. The agent can call the Core API directly when it has a suitable HTTPS execution tool and a token with the required scopes.

Prepare the material

Provide the agent with the relevant agenda notes, speaker biographies, organization ID, event ID, event dates and timezone. Describe which existing records should be kept or changed. The Core Events resource exposes the dates but not the timezone; obtain the latter from the organizer.

Keep API credentials in the execution environment’s secret store. Only share source material that the customer intends to process in that AI environment.

Use this prompt

Use the Brella Core API skill to prepare this event's agenda.

Organization ID: [our organization]
Event ID: [our event]
Event dates and timezone: [confirmed values]
API origin: [the HTTPS address provided by Brella]

Extract sessions and speakers from the attached material. Produce a table
with source IDs, title, local start time, explicit timezone offset,
duration, track, location, description and speaker identities/roles.
Mark missing values and ambiguous matches; do not guess.

Read existing speakers, tracks and sessions if you have authorized access.
Propose which records to reuse, create or update. Preserve existing
speaker assignments unless our reviewed plan explicitly replaces them.
Show one complete example and the remaining batch plan for approval.

Once the plan is authorized, execute the sample if your environment can call the API,
then verify it before the remaining approved records. Keep source IDs,
returned Brella IDs and per-item results so an interruption can be
reconciled without blindly retrying writes. Otherwise give us runnable
requests and clearly state that nothing has been imported.

Download the agenda plan template. It is a planning document, not a payload to submit to the API.

Run and verify the import

Follow the interactive agenda recipe for scopes, the speaker → track → session sequence, request builders and verification. It also explains DraftJS descriptions, replacement of speaker assignments and how to reconcile interrupted imports.

Core has no general session draft/publish input. Treat the approved import as changes to the event’s agenda; verify one sample in the organizer agenda before continuing the batch. Speaker DELETE requires a separate delete action and affects assignments; use it only for explicitly approved cleanup targets.