add_contacts_to_list
ChatGPTAdd one or more contacts to a list.
By Gomry, Inc.
Gomry is an event platform for organizers. Connect your Gomry account to run your events from ChatGPT: see what's coming up, create and edit events, change ticket prices and limits, check who registered, look up contacts, invite and message attendees, and compare sales and page views across events. Use it when you want an answer about your events or a quick change without opening the dashboard. It works on your own Gomry data and respects your team role, and ChatGPT asks you before running anything that changes your data or emails people.
type says which kind of entry the id refers to — the three do not share an id space, so a wrong type is a not-found rather than a silent mismatch. Optionally feature it to pin it to the top.years_back years before the current one (default 1) — the server computes it, so never hand-compute last year's dates. Pass baseline_from/baseline_to only for an arbitrary comparison window. Amounts are per native currency (never converted); deltas are computed per currency. Defaults the current window to the last 6 months.send_email is true (a ticket CONFIRMATION email, "Your ticket: …", which is the wrong email for an invitation) — it defaults to false, so nothing is sent unless you ask for it. Use this tool ONLY to create confirmed/already-attending tickets ("attendees") for a contact. To INVITE someone, send an invitation, add to the guest list, or handle an RSVP, use send_invite instead — NOT this tool. Delegates to the canonical service so capacity guards, invited-ticket upgrades, contact upsert, and shared paymentID all behave exactly as the dashboard.email or phone_number is required. If a contact with this email already exists, returns a 409-equivalent error with the existing record.is_private is true the event is also queued for an automatic review that can list it in Gomry's public discovery feed. Other side effects (calendar fanout, Mixpanel tracking) match the dashboard creation flow exactly. Requires name, start, and location. end is OPTIONAL — omit it and the event ends 2 hours after the start, exactly as the create page does (it has no end-date input); only send it when the caller gave an explicit end time. Returns the persisted event.name, duration_minutes, default_capacity, location, price and currency. A default "General admission" ticket class is created at that price.require_approval), which is not reachable via update_experience.hostId = event id OR experience service id). Give it a per-host price, and stock: stocks for precise per-option counts, or stock for one count across every option, or omit both for unlimited. Get the productId from list_merch_products first. One offering per product per host — offering the same product twice is rejected.options (e.g. ["S","M","L"]) for an add-on with variants like a t-shirt; omit it for a simple add-on like parking (stored with one implicit "General" option).valid_from to hold it until a later date. Provide exactly one of discount_amount (fixed, in the event currency) or percent_off (1-100) — passing both or neither is an error. Leave applied_to_tickets empty to discount every ticket class, or list ticket-class ids to restrict it; call list_ticket_classes first to get those ids. Codes are uppercased on save and must be unique within the event.name; identifier is derived from it when omitted. Nothing public is created: the space is empty until events are moved into it with move_event. Refused when the name or identifier is already used by an active space (the response lists the existing ones), and "GENERAL" is reserved for the General space every organization has. Not idempotent: retrying a successful call is refused as a duplicate.hide_on_event_page: true to create it without showing it to buyers, or a future sales_start to hold sales until then. Delegates to the same service the dashboard uses. Pass cost=0 for a free ticket. For pay-what-you-want donations, set flexible_pricing_enabled=true, cost=0, minimum_price=0; suggested_price is optional.experience_id; optionally session_ids to limit the sweep, and delete_recurrences: true to also remove every recurrence rule (active and paused) so the experience ends up with zero sessions and zero rules. Sessions with bookings are NEVER deleted — they are skipped and listed in the result; cancel those individually instead. Only experiences owned by this organization can be modified. This is destructive and cannot be undone through the API: confirm with the user before calling. Returns the deleted/skipped ids and the remaining session and recurrence counts.event_id. Only the primary host organization can delete; an event co-hosted by this organization is refused. An event that has not ended and has paid orders is refunded in full first, the organization covering the fees: the first call changes nothing and returns confirmation_required with the refunds and a confirmation_token; call again with the same event_id and that token only after the user confirms. Then sales close, the refunds run in the background (refunds_in_progress: true) and the event is deleted when they are done. A short balance answers refused with an add_funds_url (deposits cannot be made through MCP). This is destructive and cannot be undone through the API: confirm with the user before calling. Deleting an already-deleted event succeeds with already_deleted: true.experience_id. Only experiences owned by this organization can be deleted. Sessions and bookings are NOT cancelled or refunded and attendees are NOT notified. This is destructive and cannot be undone through the API: confirm with the user before calling. An unknown or already-deleted experience is reported as not found.fields to receive only the parts of the submission the question needs.fields to receive only the parts of the record the question needs.fields to narrow that to only what the question needs, so a count or a segment size returns no personal data at all. organizationId is auto-resolved from your token.list_events first to get the ids. Each event reports the same figures as get_event_conversion_rate. Ids that are not in your organization are returned under meta.rejected and the rest still compute, so one bad id does not fail the call. If page_views_available is false for an event, do NOT report 0 views for it.devices (default), browsers or os. Useful for "is my page mostly being opened on mobile". Counts page views, not registrations. event_id is required.event_id is required for every mode EXCEPT "calendar", which embeds a whole space. Return the snippet to the organizer verbatim — it is meant to be pasted, so do not reformat or summarise it. For embedding an experience (a class, workshop or bookable session) use get_experience_embed_snippet instead.interval, which only bounds the page views — the response says so. CRITICAL: when page_views_available is false the Tinybird query failed; report the registration count and say view/conversion data is unavailable, never that the event got 0 views. For several events at once use get_conversion_rates_for_events. event_id is required.list_recurrences.session_id and booking_id — bookings are stored per session, so call list_experience_bookings first to get them.experience_id is required — call list_experiences first if you do not have it. Return the snippet verbatim; it is meant to be pasted. For an EVENT rather than an experience, use get_embed_snippet.questions array. Use the id of each question to map to the question_id field on application answers.countries (default), cities, regions or continents. Derived from visitor IP on page views, NOT from attendee addresses — a visitor who never registered still counts. event_id is required.scheduled_for) and its status ("scheduled", "sent", "draft", "failed"). Use it to show an organizer what is queued, and to get the message id for get_message_content or cancel_scheduled_message.group_by: "count") or a daily series (group_by: "timeseries"). This is WEB traffic from Tinybird — who looked at the page — which is different data from query_metrics and get_sales_trends (tickets and payments). Use both to compare views against sales. event_id is required; there is no ambient event on this surface.referers (default, the referring domain), referer_urls, utm_sources, utm_mediums, utm_campaigns, utm_terms or utm_contents. This is page-view attribution from Tinybird; it is NOT the same as ticket-level referral codes or promoter attribution. For every dimension at once use get_utm_traffic_report. event_id is required.days (default 30), bucketed by UTC date. Counts tickets with status valid, checked_in or pending_approval. Days with no registrations are omitted rather than reported as zero. For cross-event trends over a date range use get_sales_trends instead. event_id is required.referers, referer_urls, utm_sources, utm_mediums, utm_campaigns, utm_terms, utm_contents) in a single response, each as rows of value + page_views sorted by page views descending. Pass dimensions to narrow it; omit for everything. This is the tool for "give me all the UTM data for this event" or an export of raw traffic attribution — use get_referrer_sources only for a single dimension. Counts VIEWS from Tinybird, NOT registrations or revenue, and is not joined to ticket-level referral codes or promoter attribution. A dimension whose status is "error" could not be measured; do NOT report it as zero. event_id is required.answers array keyed by question_id (cross-reference with get_form). Filter by form_id to analyze submissions for a single form, or by a date range to count submissions over a period — and pass fields to leave the free-text answers out of the response when the question is a count rather than an analysis. Status defaults to all (Draft, Pending, Accepted, Rejected). Results are sorted by created_at newest-first by default; pass sort to change direction. With a date filter + sort, you can early-stop pagination once results fall outside the range.fields to narrow that to only what the question needs, so a head count or a check-in rate returns no personal data. For full form submissions (answers), use list_applications with form_id instead. Status defaults to valid+checked_in. This does NOT cover experiences — experiences have bookings rather than tickets, so use list_experience_bookings for those.record_type (e.g. 'contact').status filter (active, inactive). When you belong to multiple organizations, omit organization_id to see events across all of them.version (required when updating or archiving). If the experience is in single-price mode, use_ticket_classes is false and the list is empty — pricing then comes from the experience itself. For EVENT tiers use list_ticket_classes instead.status (active, inactive). Rows carry description_preview (the first ~200 plain-text characters), not the full description — call get_experience for the whole body of one experience, and never page through every experience just to read their descriptions.list_applications to interpret answers.hostId may be an event id or an experience service id.id of an organization as the organization_id argument for other tools to scope a call to one specific org. GOMRY STAFF ONLY: when called by internal staff in GomryOS mode, this instead lists organizations ACROSS THE WHOLE PLATFORM (not just your own), each with country, niche, trailing-12-month volume and fees, and first event date — the same figures as the /gomryos Revenue Intelligence dashboard. Every organization_id returned works with the read-only tools even where you are not a member. total_count is the number of matches BEFORE paging, so answer "how many X" from that field rather than counting rows. Filters are ignored for non-staff callers.is_one_off: true are not schedules — each carries a single date added by hand via create_session, and its weekly cadence is internal plumbing that runs once and stops. Describe the experience's schedule from the is_one_off: false entries only.offsetMinutes) before every session to whoever is booked at that moment.resource_type: "experience" — note those must be edited with the update_experience_ticket_class tool, not update_ticket_class.event_id and the target space as an identifier, id or unambiguous name ("GENERAL" for the General space); list_spaces returns the valid values. Refused when the event has already sold tickets — attendees hold tickets tied to its current space, so the dashboard blocks that move too. Asking for the space the event is already in succeeds without changing anything (already_in_space: true).source (tickets or payments), a group_by dimension (event, day, week, month, ticket_class, status), and a metric (count, unique_contacts, sum_spend). Returns one row per group with the aggregated value plus a grand total. Examples: tickets grouped by event counted; payments grouped by month summed (sum_spend, per currency); tickets grouped by ticket_class counting unique_contacts. sum_spend requires source=payments. Defaults to the last 6 months. Spend is reported per native currency (never converted).type says which kind of entry the id refers to.order array must reference exactly the set of ACTIVE class IDs — extras, missing IDs, or archived IDs are rejected. Call list_experience_ticket_classes first to get the live IDs, then pass them all in the desired order.user_quote you supply verbatim, is stored and posted to an internal Gomry Slack channel. Tell the user you are logging it — never call this without saying so. Use it to log a feature request when the organizer asks for a Gomry capability that no available tool supports (e.g. an unavailable report, an unsupported automation, a missing integration). Call it BEFORE telling them it is not supported yet, then tell them you have logged the request for the Gomry team. Do NOT call it when a tool already covers the ask, when you just need to clarify what they want, or for a simple misunderstanding.fields to receive only the parts of each match the question needs.recipient_type, now or at scheduled_for: use it for a message about that event, such as a reminder, a schedule change or venue details. There is no per-recipient confirmation and a sent email cannot be recalled, so confirm the audience and the copy with the user before calling. recipient_type picks registration statuses: ["accepted"] for people who hold a valid ticket, "pending" for those awaiting approval, "rejected" for declined ones, ["all"] (the default) for everyone registered. ticket_class_ids narrows it to specific tiers (ids from list_ticket_classes). Pass scheduled_for as an ISO-8601 instant to send later, one call per message; omit it to send now. A scheduled message can be called off with cancel_scheduled_message until it fires. Emails go out from the organization's reply-to address, and unsubscribed contacts are skipped automatically. To reach contacts who are not registered for the event, use send_contact_message instead. A WhatsApp copy goes out automatically to recipients who opted in to WhatsApp, and is NOT counted in queued: the result's whatsapp gives how many were queued, a plain status (why none, if none) and billing (null until WhatsApp billing is enforced): the free messages it uses, the estimated cost from the organization's WhatsApp balance, and copies nothing covers or that billing stopped. Recipients still get the email either way.contact_ids) or every contact on a saved list (list_id), and also reaches them by SMS and push where they have opted in: use it for news or an announcement to the organization's contacts, whether or not they are registered for an event. A sent message cannot be recalled, so confirm the recipients and the copy with the user before calling. It does not send WhatsApp. To message the people registered for one event, use send_blast_message instead; to invite one contact to an event, use send_invite. Unsubscribed contacts are skipped automatically.scheduledFor. Pass sessionId to reach just one session ("remind tomorrow's yoga attendees"). Recipients are fixed when the message is queued, so people who book after a scheduled send is created will not get it. For "N minutes before every session", use createSessionMessageAutomation. Confirm the audience and copy with the user before calling. A WhatsApp copy goes out automatically to recipients who opted in to WhatsApp, and is NOT counted in queued: the result's whatsapp gives how many were queued, a plain status (why none, if none) and billing (null until WhatsApp billing is enforced): the free messages it uses, the estimated cost from the organization's WhatsApp balance, and copies nothing covers or that billing stopped. Recipients still get the email either way.invited ticket for them (no ticket class, no charge). There is no way to call this without mailing someone, so confirm the recipient with the user first. Use it for any invitation, "add to the guest list", or RSVP request. This is the dashboard "Send invitations" flow: delivery is asynchronous (queued), and recipients who are unsubscribed or already have a ticket are skipped. To create a confirmed ticket with a confirmation email instead, use create_attendee. DELIVERY: the email invite always goes out. A WhatsApp copy is sent automatically (never chosen by the caller) and only to invitees who have a phone number on file, have opted in to WhatsApp, and whose notification preferences include WhatsApp for invites (US/Canada +1 numbers default to SMS instead). The result reports whatsapp_queued and a plain-language whatsapp_status; queued does NOT include the WhatsApp copy. Answer "was a WhatsApp invite sent?" from those fields rather than assuming. The organization pays for WhatsApp (free messages each month, then billed and charged later, like Gomry Ads): whatsapp_billing (null until billing is enforced) gives the free messages used, the estimated cost, the copies that won't go out, and why billing stopped the copy (whatsapp_off, payment_failed).notify_applicant is true — up to 200 acceptance or rejection emails from a single call. notify_applicant is REQUIRED and has no default, so decide it with the user before calling. The tool approves, rejects, or returns form submissions to review, in bulk: pass one or more application IDs from list_applications and the target status. Accepting with notify_applicant true sends the form's acceptance email and adds the applicant to the form's accepted contact lists; rejecting sends the rejection email. Both only mail when the form has that template active. IDs that cannot be moved come back in failed with a reason rather than failing the whole batch.metadata is a free-form key/value object — your own data (e.g. a cohort tag or external funnel stage), merged onto the existing metadata. Pass null as a value to clear a key. The application's internal status is not writable here (it drives acceptance emails and list membership). Returns the updated application with its change history.sizes (the FULL list, echoing back each existing size’s id from get_bundle). Changing sessions, prices or sizes affects only FUTURE buyers: anyone who already paid keeps exactly what they bought. Set status to "archived" to stop sales while keeping it readable for existing holders.links replaces the whole object rather than merging.status: 'inactive' to archive (soft-delete) a contact.start by more than 6 hours while the event has paid orders EMAILS EVERY ATTENDEE and lets every buyer cancel for a full refund for up to 48 hours (the organization covers the fees). Snake_case body, partial update — only the fields you pass are written. NOTE: venue REPLACES the existing venue wholesale rather than merging, so send every venue field you want to keep. reviews shows or hides the attendee reviews on the public event page (public) and those borrowed from past dates (past_dates); both stay on while the Distribution Program is enabled. Delegates to the canonical update service (taxonomy sync, cache invalidation, isPast recompute all fire). That date move takes two calls: the first changes nothing and returns confirmation_required with what buyers could claim and a confirmation_token; call again with the same arguments and that token only after the user confirms.cover_image, an uploaded https URL), swap the full photo gallery (photos, first entry is the cover), rename it, edit the description, activate/deactivate it (status), make it secret / link-only (is_private, the same setting as a private event), open/close bookings (registration_status), change the price, currency, per-session capacity or session length. Partial update — only the fields you pass are written. Changing the currency cascades to every ticket tier.version from list_experience_ticket_classes. Capacity cannot drop below the tier's live sold count (the tool returns the real count if you try). Currency is not editable here: it stays in lockstep with the experience's currency.remove_member and re-invite them to the target scope from the Gomry dashboard.price, currency, and/or per-option stocks. Stock rows are upserted — options you do not list keep their current stock. To only change stock, update_merch_stock is simpler.addOptions, remove existing ones with removeVariantIds). Pass only what changes. Editing the template updates it everywhere it is offered.stocks with a { variantId, stock } entry per option (get the ids from list_merch_offerings); for a single-option add-on you can pass a plain stock number. Unlisted options keep their stock.logo (the URL of an image already hosted somewhere) OR the image file itself as logo_base64 + content_type, which uploads it to Gomry's storage and attaches it in one step; prefer logo_base64 when the user supplies an actual file rather than a link (JPEG, PNG, WebP, or GIF; max ~3MB decoded). Social links accept either a full URL or a bare handle like "@gomry", which is expanded to that network's URL. This changes the org's public identity wherever it is shown, so confirm the new values with the user before calling. Does NOT change payment settings, webhooks, tax details, billing country, or the org URL/username.status. Pass only the fields to change.event_id or experience_id. enabled: false deactivates sponsors entirely (every ad placement plus the cashback program); enabled: true activates them. Or toggle features individually: post_purchase_dialog and ticket_placement (events only), experience_page (experiences only), cashback_enabled (both). This changes what attendees see at checkout and what advertisers can buy, so CONFIRM WITH THE USER before calling. Idempotent: the response lists what actually changed and the resulting state. There is no separate read tool on this surface: current_state in the response IS the current state, and a call that requests settings already in effect changes nothing and returns an empty changes list.Click any prompt to copy it.
Add this badge to your site or README. It links to this page.
HTML
<a href="https://mcp-app-store.keenethics-labs.com/app/gomry"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>
Markdown
[](https://mcp-app-store.keenethics-labs.com/app/gomry)