{"id":"692e3a9e4bc73507d7a4afd2","title":"Meetup Settings","path":"how-to/committee/walks/meetup-settings","contentMarkdown":"# Meetup Settings\n\nThe Meetup integration lets you automatically publish your group walks to a connected Meetup group, so when a walk is approved on NGX-Ramblers it appears as a Meetup event for members to RSVP to.\n\n> **Important: The Meetup API integration is currently unavailable.**\n>\n> The Meetup public API now requires a [Meetup Pro subscription](https://www.meetup.com/pro/), which is prohibitively expensive for most Ramblers groups. We are tracking a replacement approach that avoids the API entirely - see [Issue #230: feat(meetup): add manual paste/scrape publishing option to avoid Pro subscription](https://github.com/nbarrett/ngx-ramblers/issues/230) for progress.\n>\n> In the meantime, the configuration UI is still present and you can save settings, but walks will not actually be synchronised to Meetup. If you rely on Meetup for your walks programme, you will need to manage events directly on Meetup for now.\n\n## When This Feature Applies\n\nThe Meetup integration is independent of your group's Walk Population mode (Local or Walks Manager) - the Publish to Meetup option appears on individual walks regardless of where the walk data comes from.\n\nIt does, however, depend on having an active Meetup group and an OAuth-authorised connection between NGX-Ramblers and Meetup. Once the API integration is restored (or replaced with a paste/scrape alternative as per [issue #230](https://github.com/nbarrett/ngx-ramblers/issues/230)), this is the part that will need to be set up.\n\n## How It Works (When the API Is Available)\n\nThere are three layers to the Meetup integration:\n\n1. **System-level OAuth setup** - one-time admin task to authorise NGX-Ramblers to talk to your Meetup group\n2. **Group-level publishing defaults** - default values for description, RSVP limit, and announce flag that apply to every walk\n3. **Per-walk publishing** - walk leaders enable Meetup publishing on individual walks and optionally override the defaults\n\nWhen a walk with Meetup publishing enabled is saved, the system creates or updates a corresponding Meetup event. When publishing is disabled or the walk is deleted, the Meetup event is removed.\n\n## Setting Up the Meetup Connection\n\nThis is in **Admin > System Settings > External Systems > Meetup**:\n\n1. Enter your **Group URL**, **Group Name**, and **API URL**\n2. Enter your **Client ID** and **Client Secret** from Meetup's OAuth app registration (use the **View OAuth Clients** link to find or create one at meetup.com)\n3. Set the **Client Redirect URL** to your site's callback URL\n4. Click **Initiate Request Authorisation** to start the OAuth flow\n5. Authorise NGX-Ramblers on Meetup\n6. The access token and refresh token are captured automatically when you return\n7. Click **Save**\n\nThe refresh token is used to keep the connection alive without you needing to reauthorise.\n\n## Configuring Publishing Defaults\n\nThis is in **Admin > Walks > Meetup Settings**, with two sub-tabs:\n\n### Maintain Description Content\n\nCreate reusable description prefixes that can be selected per walk. These are stored as Content Text snippets and let you maintain a consistent intro for your Meetup events without retyping it on every walk.\n\n### Publishing Defaults\n\nSet the global defaults that apply to new walks:\n\n- **Description prefix** - which Content Text snippet to use as the default\n- **Publish status** - whether new events should be created as Draft or Published\n- **RSVP limit (guest limit)** - how many guests each member can bring (1-10)\n- **Announce checkbox** - whether to announce the event to the Meetup group on publication\n\n## Publishing an Individual Walk to Meetup\n\nWhen editing a walk, walk leaders see a **Meetup** tab:\n\n1. Tick **Publish this walk to Meetup**\n2. Optionally override the defaults:\n - Choose a different description prefix\n - Change publish status (draft/published)\n - Adjust the RSVP limit\n - Set the announce flag\n3. Edit the walk-specific Meetup description text (which gets prefixed with the chosen Content Text snippet)\n4. Save the walk\n\nWhen the walk is saved (and the API integration is working), the system:\n\n- Checks if a Meetup event already exists for this walk\n- If yes, updates the event with the latest details\n- If no, creates a new Meetup event\n- Stores the Meetup event URL on the walk so it appears as a \"View on Meetup\" link\n- Matches or creates the venue on Meetup based on the walk's start location\n\nIf you untick **Publish this walk to Meetup** and save, the corresponding Meetup event is deleted.\n\n## Permissions\n\n- **System OAuth setup** - requires System Admin\n- **Publishing defaults** - requires Walk Admin\n- **Per-walk Meetup settings** - requires Walk Admin or the walk leader for that walk\n\n## Current Status\n\nUntil the Meetup API integration is restored (or replaced - see [issue #230](https://github.com/nbarrett/ngx-ramblers/issues/230)):\n\n- You can still configure all the settings on this page\n- The Publish to Meetup checkbox still appears on individual walks\n- Saving a walk will not create or update a Meetup event\n- Existing Meetup events that were published before the API became unavailable are unaffected, but will not be updated when the corresponding NGX-Ramblers walk is updated\n\n## Related Guides\n\n- [Add Walk Slots](https://ngx-ramblers.org.uk/how-to/committee/walks/add-walk-slots) - create walks ready for leaders to claim\n- [Walk Leader Contact Settings](https://ngx-ramblers.org.uk/how-to/committee/walks/leader-contact) - configure how visitors contact walk leaders\n- [Ramblers Walk Export](https://ngx-ramblers.org.uk/how-to/committee/walks/export) - export walks to upload to Ramblers Walks Manager","contentHtml":"

Meetup Settings

\n

The Meetup integration lets you automatically publish your group walks to a connected Meetup group, so when a walk is approved on NGX-Ramblers it appears as a Meetup event for members to RSVP to.

\n
\n

Important: The Meetup API integration is currently unavailable.

\n

The Meetup public API now requires a Meetup Pro subscription, which is prohibitively expensive for most Ramblers groups. We are tracking a replacement approach that avoids the API entirely - see Issue #230: feat(meetup): add manual paste/scrape publishing option to avoid Pro subscription for progress.

\n

In the meantime, the configuration UI is still present and you can save settings, but walks will not actually be synchronised to Meetup. If you rely on Meetup for your walks programme, you will need to manage events directly on Meetup for now.

\n
\n

When This Feature Applies

\n

The Meetup integration is independent of your group's Walk Population mode (Local or Walks Manager) - the Publish to Meetup option appears on individual walks regardless of where the walk data comes from.

\n

It does, however, depend on having an active Meetup group and an OAuth-authorised connection between NGX-Ramblers and Meetup. Once the API integration is restored (or replaced with a paste/scrape alternative as per issue #230), this is the part that will need to be set up.

\n

How It Works (When the API Is Available)

\n

There are three layers to the Meetup integration:

\n
    \n
  1. System-level OAuth setup - one-time admin task to authorise NGX-Ramblers to talk to your Meetup group
    2. \n
  2. Group-level publishing defaults - default values for description, RSVP limit, and announce flag that apply to every walk
    3. \n
  3. Per-walk publishing - walk leaders enable Meetup publishing on individual walks and optionally override the defaults
    4. \n
\n

When a walk with Meetup publishing enabled is saved, the system creates or updates a corresponding Meetup event. When publishing is disabled or the walk is deleted, the Meetup event is removed.

\n

Setting Up the Meetup Connection

\n

This is in Admin > System Settings > External Systems > Meetup:

\n
    \n
  1. Enter your Group URL, Group Name, and API URL
    2. \n
  2. Enter your Client ID and Client Secret from Meetup's OAuth app registration (use the View OAuth Clients link to find or create one at meetup.com)
    3. \n
  3. Set the Client Redirect URL to your site's callback URL
    4. \n
  4. Click Initiate Request Authorisation to start the OAuth flow
    5. \n
  5. Authorise NGX-Ramblers on Meetup
    6. \n
  6. The access token and refresh token are captured automatically when you return
    7. \n
  7. Click Save
    8. \n
\n

The refresh token is used to keep the connection alive without you needing to reauthorise.

\n

Configuring Publishing Defaults

\n

This is in Admin > Walks > Meetup Settings, with two sub-tabs:

\n

Maintain Description Content

\n

Create reusable description prefixes that can be selected per walk. These are stored as Content Text snippets and let you maintain a consistent intro for your Meetup events without retyping it on every walk.

\n

Publishing Defaults

\n

Set the global defaults that apply to new walks:

\n\n

Publishing an Individual Walk to Meetup

\n

When editing a walk, walk leaders see a Meetup tab:

\n
    \n
  1. Tick Publish this walk to Meetup
    2. \n
  2. Optionally override the defaults:\n
    3. \n
  3. Edit the walk-specific Meetup description text (which gets prefixed with the chosen Content Text snippet)
    4. \n
  4. Save the walk
    5. \n
\n

When the walk is saved (and the API integration is working), the system:

\n\n

If you untick Publish this walk to Meetup and save, the corresponding Meetup event is deleted.

\n

Permissions

\n\n

Current Status

\n

Until the Meetup API integration is restored (or replaced - see issue #230):

\n\n

Related Guides

\n\n"}