add-guest
ChatGPTName a person on one of a company's invitation places, as the company itself would on its invitation page, for example when the company emails you their names. The guest's ticket is emailed to them straight away. guest holds the event's guest form fields, keyed as get-event lists them under guest_form (usually firstname, lastname, email, company, jobtitle, mobile). If the invitation is full, raise its places with update-invitation first.
add-ticket-type
ChatGPTAdd a kind of ticket to one of your events, such as "Standard", "VIP" or "Delegate", with its price in euro (0 for free) and an optional limit on how many can be issued. Invitations draw their places from a kind of ticket too.
change-guest
ChatGPTCorrect a named guest's details, or replace them with someone else on the same place. Only the fields you pass change. When the email address changes, a new ticket is emailed to the new address and the previous ticket stops working, so confirm with the organiser first. A ticket already used at the door cannot be changed.
create-event
ChatGPTCreate a new event for your organisation. It is saved as a draft unless status is "published". Times are Malta local time (for example 2026-11-20 19:30). A venue is matched to an existing one by name or added as new. Add the kinds of ticket next with add-ticket-type; a public event cannot sell tickets without one.
create-invitations
ChatGPTInvite one or more companies to one of your events, each with a contact email and a number of places. Invitations are saved as drafts: nothing is emailed until send-invitations. If any company cannot be added (a bad email address, or not enough places left on the ticket), none are added and the reason is given per company.
get-event
ChatGPTEverything about one of your events: details and programme, dates (Malta time), venue, status, the kinds of ticket with how many were issued and how many places are left, sales totals, invitation totals, and the guest form (the fields add-guest needs for each guest).
get-guest-list
ChatGPTWho holds a ticket for one of your events: name, company, position, kind of ticket, the company that invited them, and when they were checked in. Email addresses and mobile numbers are left out unless include_contact_details is true; ask for them only when the task needs them. Guests named on an invitation have a guest_id, which change-guest and remove-guest take.
list-call-sheet
ChatGPTThe team's call sheet (events.com.mt/callsheet): people and companies to ring, grouped in tabs, with why, how the call went, who is handling it, when it was made and the day to ring back. show: pending (the default), done, due (call-backs due today or overdue, on every tab) or all. Rows linked to an invitation show whether the company has answered since. The summary counts the whole sheet and lists the tabs and the team members to assign.
list-invitations
ChatGPTThe companies invited to one of your events: contact, places given and used, status (draft, sent, opened, accepted, declined, revoked), reply deadline, reminders sent, and the invitation link the company uses to name its people. Use "awaiting" to find companies that have not answered yet. last_email says what became of the latest invitation or reminder email: sent, delivered, opened, failed (with the reason) or complained (marked as spam). Only organisers who send through their own Mailgun get past "sent".
list-my-events
ChatGPTThe events this account runs on Events.mt, with their slug (used by every other tool), status, dates (Malta time), venue, whether they are public or by invitation, and how many tickets have been issued and checked in. Upcoming events by default.
list-orders
ChatGPTTicket orders placed for one of your events through the website: order reference, buyer's name, number of tickets, amount and status (paid, pending, cancelled, failed), newest first, with totals for paid orders. Places given through invitations are in get-guest-list instead. Buyers' email addresses are left out unless include_contact_details is true.
manage-call-sheet
ChatGPTChange the team's call sheet. action: - create: someone to ring (name, phone, why in info, tab), or a company from an invitation (invitation_id) with its contact's details. - create_many: up to 500 rows at once (rows), for a list prepared elsewhere. Rows naming an invitation already on the sheet are skipped. - update: record how a call went (notes, done, contact_person), set a day to ring back (follow_up_at, follow_up_time), hand it to a team member (assigned_to). Only the fields given change. done=true records when and by whom. - delete: take a row off the sheet. - add_from_invitations: put an event's invited companies on a tab named after the event, for example those that have not answered (which=awaiting). Companies already on the sheet are left as they are. Nobody is called, messaged or emailed by this tool.
remove-guest
ChatGPTRemove a named guest from a company's invitation: their ticket is cancelled and the place is free for the company to use again. The guest is not emailed. A ticket already used at the door cannot be removed. Confirm with the organiser first.
send-invitations
ChatGPTEmail invitations to the companies' contacts. Pass invitation_ids to send particular ones, or leave them out to send every draft for the event. Emails go to real people, so confirm the list with the organiser first. An invitation that was already sent goes again as a reminder; a declined one is reopened. Revoked invitations are skipped.
send-reminders
ChatGPTEmail a reminder to companies that still have places to fill. Pass invitation_ids for particular companies, or all_with_places_left true for every sent invitation that is still open and not full. Emails go to real people, so confirm with the organiser first. Events can also remind companies automatically (see update-event, automatic_reminders).
update-event
ChatGPTChange one of your events. Only the fields you pass change. Status can move between draft and published; a finished or cancelled event keeps its status. access switches between a public event and one by invitation only (hidden from listings). Times are Malta local time. People who already hold tickets are not told about changes automatically.
update-invitation
ChatGPTChange an invitation: the number of places (for example when a company asks for more), the company name, the contact, or the reply deadline. Only the fields you pass change. Places cannot go below the people already named. Nothing is emailed.
update-ticket-type
ChatGPTChange a kind of ticket on one of your events: its name, price, limit, or whether it is on sale. Only the fields you pass change. A limit cannot go below the number already issued, and a new price applies to tickets bought from now on.
withdraw-invitation
ChatGPTWithdraw an invitation. A draft that was never sent is deleted. A sent invitation is revoked: its link stops working and the tickets of everyone the company named are cancelled, unless they were already used at the door. This cannot be undone, so confirm with the organiser first.
add-guest
Claudeadd-ticket-type
Claudechange-guest
Claudecreate-event
Claudecreate-invitations
Claudeget-event
Claudeget-guest-list
Claudelist-invitations
Claudelist-my-events
Claudelist-orders
Clauderemove-guest
Claudesend-invitations
Claudesend-reminders
Claudeupdate-event
Claudeupdate-invitation
Claudeupdate-ticket-type
Claudewithdraw-invitation
Claude