Skip to main content

Mobilize integration

Pull your events in directly from Mobilize

Get your events from mobilize.us to populate your Run events page. When users click the RSVP buttons, they'll be sent to the original Mobilize event page to complete the RSVP process.

To get your Mobilize Organization ID, log into Mobilize to access your team. In the sidebar, navigate to "Settings" and your Organization ID is shown at the top.

On the events page sidebar, select Mobilize from the Event Integrations tab, and put your Mobilize Organization ID in the input box. Your events should automatically populate the events page.

Refreshing your calendar

Run will automatically pull in your event updates every 30 minutes. If you need a faster update, visit the Events page on your Run site, give it a few seconds to pull in the new events, and then Publish your site.

Occasionally, people set their Mobilize events to a private status which will also prevent it from showing up. Check your main Mobilize page - if the events aren't being listed there either, that's likely the cause.

Filtering by Mobilize tags

Mobilize does not directly provide a method of filtering events by tag in their API. However, we've provided a workaround to accomplish this, though it requires adding a snippet of custom code to your website.

We insert CSS classes into Mobilize events. All Mobilize events receive the class "mobilize-event" and an receive an additional class for each tag associated with it, in the format of “mobilize-tag-tagname” (with spaces or punctuation in the original tag converted into dashes). By using the following CSS code, you can show only those events that contain the tags you want. You'll repeat the line below that includes "display: revert" for all tags you'd like to include.

<style>
.mobilize-event {display: none;}
.mobilize-tag-community-service { display: revert; }
</style>

You'll want to place the code above into the Custom Code section of the page or the whole site.

Custom code will not run in the CMS for security reasons, so you'll need to publish to see the filtering actually work.

Did this answer your question?