Tools · Events

The community's calendar: upcoming events and who's going, a new event (online, in person or hybrid) with its ticket on sale, changes to date, location or banner, the live stream and your own RSVP.

Each tool carries a badge: Read-only changes nothing, Changes creates or changes something right away, and Asks to confirm only acts after your yes to a summary. See Money and confirmation.

#In short

#list_events

Read-only

List events. The community's events. Minimum role: any.

With from/to or undated, the answer is { items, truncated, undated_count }: truncated says there were more than 300 events in the period, and undated_count, how many events have no date.

Returns: the events, with id, title, start, end, type (online, in person, hybrid) and location, status (DRAFT or PUBLISHED), publishedAt, updatedAt and visibility.

Ask like this: "What are the upcoming events?"

Without space_id, the tool now lists the events of every Events space. Each event says whether it issues a certificate; owners and admins also see the setting (whether it is on, the template, the text, the workload that will print and the warning for an archived template), and whoever confirmed sees the state of their own certificate.

#list_event_attendees

Read-only

Who RSVP'd. An event's participants. Minimum role: any.

Returns: the participants, with name and answer.

Ask like this: "How many people confirmed for Thursday's meetup? List the names."

Notes: whoever bought the ticket already shows in this list as Going: the purchase confirms attendance.

#create_event

Changes

Create event (with optional ticket). Events space → event → (optional) the ticket, a one-time product that unlocks the space, with stock. Minimum role: moderator or finance; with a ticket, or when creating the space, admin.

Returns: the space, the event (id, title, slug, status, start, end, visibility and, in a moderated space, moderation_status) and the ticket (id, title, price, stock, status), if any.

Draft and publishing. create_event creates the event as a draft, applies the badge, the images and the ticket, and only then publishes it, like the app's Publish: the ticket goes on sale once the event is live. To publish, the event needs a title, start, end, location (in person or hybrid) and the ticket type (the event's product, always created). If something is missing, nothing is undone: the event stays a draft, publish_missing lists what is missing (field, argument, message), draft_notice says so, and the next steps are update_event (what to fill in) and publish_event.

Ask like this: "Create the November Meetup, in person, on 11/15 from 7 to 10 p.m. at Espaço Paulista, Rua Augusta 1500, São Paulo, with 80 tickets at US$ 20 as a draft."

create_event accepts certificate (enabled, template_id, text), for owners and admins only. Turning it on requires end, is not retroactive and sends nothing right away; without template_id, the Platform default applies. The answer says that whoever has "going" when the event ends gets the certificate by email about 1 hour later (between 1h and 1h15), and that an archived template stops issuing. The text accepts {nome}, {assunto} (or {evento}), {data} and {cargaHoraria}. See recipe 28.

Every event is created with its own product (Event kind, free draft), and the response carries product and the next steps: set the price, the seats (update_product with capacity) and publish (publish_product). Publishing the event already puts the draft ticket types on sale; a paid type only with approved business information. ticket now sets up that product instead of creating another. Whoever buys the event's ticket has their attendance confirmed at once (Going), taking a seat. See Selling tickets.

Notes: A moderator without space_id is refused at the space step, because creating a space requires an admin: as a moderator, pass an existing events space.

#update_event

Changes

Edit an event. Changes the title, description, dates, type, location, address, stream link, visibility and the banner, of a published event or a draft. Only the fields sent change. Minimum role: moderator or finance.

Ask like this: "Move tomorrow's meetup to Thursday, same time."

Editing at the same time. If someone saved the event (in the app or in another conversation) after the version you read, nothing changes: the error carries current_updated_at and the open_link next step, to read the event again and repeat. On a draft, the answer suggests publish_event, or what is still missing to publish.

recording_file_url (a link, video up to 2 GB) or recording_file_base64 (about 7 MB), with recording_file_type and recording_file_name, store the event's recording on Memberfy, in a private area: it replaces the previous one and shows to those who can attend. To take it off, remove_event_recording; for the 1-hour link, get_media_url. Minimum role: moderator (or finance). See Event recording.

update_event accepts the same certificate as create_event (enabled, template_id, text), for owners and admins only; a moderator edits the event, but a call with certificate is refused. Omitted, the event certificate is not touched. Turning it on for an event that already ended works, but the assistant warns that nobody gets a certificate from it.

#publish_event

Asks to confirm

Publish an event. Publishes a draft, like the app's Publish: the event shows up (or goes to the space's moderation), enters the Feed, the draft ticket types go on sale and the event.created webhook fires. Minimum role: moderator (owner, admin, moderator and finance).

How it confirms. With the notice on, the first call returns the event and how many people get the e-mail (never who); the assistant shows the summary and only publishes after your yes. With notify_by_email: false, it publishes on the first call, quietly, and that event won't send the notice later.

When it refuses. A draft with something missing is refused before confirming, with missing and the update_event step. An event already published: refused (409).

Ask like this: "Publish the December Meetup draft, without sending e-mail."

#start_live_stream

Changes

Start live stream. Marks an event as live, with the stream link and service, if any. Minimum role: moderator or finance.

Ask like this: "We're live: mark today's live session with the link https://youtube.com/…"

Notes: afterwards, the response suggests ending the stream when it's over.

#stop_live_stream

Changes

End live stream. Minimum role: moderator or finance.

#rsvp_event

Changes

Answer event invitation. Says whether you're going to an event. Role: owner, admin, moderator or member.

Ask like this: "RSVP me to the November Meetup."

After the end, going and maybe return 409 and only not_going is accepted; the answer explains this. An event with its product published and priced answers 403 to whoever hasn't bought it (with the price; the purchase is made in the app), and a full event answers 409 (sold out), with the offer of join_waitlist. When the event issues a certificate, the answer reminds you that only "going" at the end of the event counts: "maybe" does not.

#delete_event

Asks to confirm

Delete event. Minimum role: admin.

Returns: on the first call, the title, the date and how many people RSVP'd, and the confirmation code.

Deleting the event also archives its product, and is refused (409) while there's a paid purchase that still gives access.

#remove_event_recording

Asks to confirm

Remove the recording. Deletes the event's hosted recording file for good and gives the storage back. On the first call it shows the event; on the second, with the confirmation_token, it removes. Minimum role: moderator (or finance).

#list_event_categories

Read-only

Event categories. The event categories, with the value and the translated name: the values create_event and update_event take in category. Minimum role: any.

Parameters: none.

Returns: each category, with the value (e.g. workshop) and the name in the connected person's language.

Ask like this: "Which event categories are there?"

#register_member_for_event

Changes

Register someone for the event. The team registers a person from the community (going) for an event that doesn't charge them, with the rules of the person's own registration: an event that has already ended, required questions and seats. The person gets the confirmation e-mail. Runs on the first call. Role: owner, admin or moderator.

Ask like this: "Register Maria for Thursday's meetup."

#Registration questions

6 tools for an event's registration questions. See Events › Registration questions.

rsvp_event takes answers: on an event with required questions, the first call without them comes back with the questions and what comes from the profile, and the assistant asks before confirming. Answers stay out of the audit log.

Ask like this: "Ask company, job title and CPF on the November Meetup registration, with the CPF at the door", "Who hasn't answered the event questions yet?", "Confirm my attendance at the November Meetup".

#Event check-in

11 tools for door check-in. See Events › Check-in.

create_event and update_event take check_in_enabled; turning check-in on suggests create_event_kiosk. An event organizer can be a member, so the door tools show for every role and the route decides. The ticket token, the QR and the kiosk link stay out of the audit log. The ready-made prompt Event door (run_event_door) walks through check-in in the conversation.

#Ticket types and batches

claim_free_product takes quantity and registration_answers; refund_purchase takes ticket_ids (not together with amount), and the summary before confirmation lists the tickets and the amount of each.

Ask like this: "Create the conference's half-price ticket at $60, 100 seats, with proof at the door", "How much did each batch sell?", "Give my second ticket to [email protected]."

#Related

• Tools
• Recipes
• Money and confirmation