---
category: "News"
title: "Gomry now integrates with Zapier"
meta_description: "Connect event registrations, applications and guest lists to your existing tools with Gomry’s new Zapier integration."
canonical: "https://business.gomry.com/blog/gomry-zapier-integration/"
comparison_date: "2026-10-22"
cta_label: "Open Gomry on Zapier"
cta_url: "https://zapier.com/apps/gomry/integrations"
image_url: "https://business.gomry.com/uploads/gomry-zapier.png"
image_alt: "Gomry integration page on Zapier."
image_width: 3840
image_height: 2160
---

# Gomry now integrates with Zapier

A new event registration in Gomry can now create or update a contact in HubSpot, without someone exporting a list and copying the details across. Gomry’s Zapier integration also lets you send application alerts to Slack and add guests from a shared Google Sheet.

Zapier connects apps through workflows called Zaps. A trigger in one app starts an action in another: a registration in Gomry, for example, can tell HubSpot to update a contact. You configure the connection for the work your team needs to do.

## Bring attendee details into HubSpot

Choose Gomry’s New Attendee trigger and HubSpot’s Create or Update Contact action. Map the attendee’s email and name to the contact fields, and include an event reference in the HubSpot properties you choose. The email lets HubSpot create a contact or update the existing one.

Your team can then see which event that person registered for when preparing a follow-up, rather than rebuilding the context from a separate ticket export. The trigger sends the attendee’s details, which may differ from those of the person who bought the tickets.

New Attendee starts once per ticket registered through checkout, including free, paid and pending-approval registrations. A group order can therefore start several runs. The trigger records registration, not proof of payment, approval or attendance.

## Send exhibitor applications to Slack

For an event accepting exhibitor applications, a submission can notify the selection team in the channel it already uses. Connect Gomry’s New Form Response trigger to Slack’s Send Channel Message action, then map the applicant’s name, business and relevant answers from your form into the message.

The team receives the information it needs to begin reviewing the application, without someone forwarding each submission. You choose the channel and which answers to include; a submitted application starts the workflow, not a saved draft.

For a notification about a particular decision, use Updated Form Response and add a filter for the relevant status. That trigger also covers other changes to submitted responses, so the filter is what makes an acceptance-only or rejection-only notification specific.

## Turn spreadsheet rows into event guests

Your team might keep sponsor guests in a shared Google Sheet. Use Google Sheets’ New Spreadsheet Row trigger with Gomry’s Add Attendee action, choose the existing Gomry event and ticket class and map the guest’s name and email from the row.

When a new row starts the Zap, Add Attendee adds the guest to that event with a complimentary ticket, without taking a payment. Staff can work from the shared guest sheet rather than entering the same person again in Gomry.

These guest-list additions do not start Gomry’s New Attendee trigger. The HubSpot workflow above starts with checkout registrations, so adding a guest through this Zap does not automatically set that second workflow running.

## Bring other records into Gomry

An external form can also start a Zap that creates a contact in Gomry. With Create or Update Contact, a matching email updates the existing profile rather than creating another contact for that address. The action applies the fields you map for that run; it is not an ongoing synchronization of every contact in both apps.

If your team prepares event information in another tool, a Zap can pass those details to Gomry’s Create Event action to create the event there.

## Set up your first connection

1. Create a Zap in Zapier and choose Gomry as the trigger or action app for your workflow.
2. In Gomry, open Organization Settings → API Keys and generate a key with the permissions the workflow needs. An authorized user of the organization must create it.
3. Connect Gomry to Zapier using that key, and connect the other app you want to use.
4. Configure the trigger and action, map the fields and test the flow with a suitable sample. Check that the destination receives the attendee, application or guest details you intended.
5. Turn on the Zap so it can run for new matching activity.

Gomry’s [API key instructions](https://docs.gomry.com/authentication#generating-an-api-key) and [permissions reference](https://docs.gomry.com/scopes) cover the connection details. Keep the key private and give it the access required for the workflow.

## Availability and costs

Gomry is publicly available in the Zapier directory, where the integration is currently labeled Beta. It works with free Gomry accounts too, with no additional Gomry charge for using the integration.

The New Attendee, New Form Response and Updated Form Response triggers used above are listed as Instant and use Gomry webhooks to start the Zap. The time needed to complete the next action also depends on Zapier and the connected app.

Zapier has its own task allowances and plan requirements. Multi-step Zaps and Premium apps require a paid Zapier plan, and the connected apps may have their own subscription requirements. Your workflow and how often it runs determine what you need; see [Zapier’s current plans](https://zapier.com/pricing).

## Sources

### Zapier

- [Gomry integration and supported events](https://zapier.com/apps/gomry/integrations)
- [HubSpot contact actions](https://zapier.com/apps/hubspot/integrations)
- [Slack messaging actions](https://zapier.com/apps/slack/integrations)
- [Google Sheets row triggers](https://zapier.com/apps/google-sheets/integrations)
- [Plans and task allowances](https://zapier.com/pricing)

### Gomry

- [Organization API keys](https://docs.gomry.com/authentication#generating-an-api-key)
- [API permissions](https://docs.gomry.com/scopes)

**Create your first Zap with Gomry.**
