Skip to main content

Mighty Networks Integration

Mighty Networks Integration Why: Seamlessly connect your Mighty Networks account to automate member management. This integration allows you to auto...

Written by Ken Truesdale

Platform 2 Guide — This article applies to the new platform. Looking for classic platform docs? Browse the Platform 1 collection.

Why: Seamlessly connect your Mighty Networks account to automate member management. This integration allows you to automatically create members and grant access based on their plan purchases, saving you time and enhancing your members' experience.

Navigate: App Station > Settings > Integrations > Mighty Networks

Quick Start

  1. Enable the integration in App Station.

  2. Copy the generated bearer key into Mighty Networks under Network Admin > Integrations > Webhooks.

  3. Paste the Member Kitchens webhook URL and select the following events:

    • MemberPurchased

    • MemberSubscriptionRenewed

    • MemberSubscriptionCanceled

    • MemberRemovedFromPlan

    • MemberPlanChanged

  4. Map each Mighty plan to an access level, including optional trial days (0-30).

  5. (Optional) If using the Admin API, paste your network ID and API key to sync tags and badges.


Detailed Setup Instructions

Enabling the Integration

  1. Go to App Station and navigate to Settings > Integrations > Mighty Networks.

  2. Enable the integration. This action generates a bearer key that you will use in Mighty Networks.

Configuring Mighty Networks

  1. In your Mighty Networks admin panel, go to Network Admin > Integrations > Webhooks.

  2. Paste the Member Kitchens webhook URL and the bearer key you copied earlier.

  3. Select the following events to enable:

    • MemberPurchased: Triggers when a member purchases a plan.

    • MemberSubscriptionRenewed: Triggers when a member's subscription is renewed.

    • MemberSubscriptionCanceled: Triggers when a member cancels their subscription.

    • MemberRemovedFromPlan: Triggers when a member is removed from a plan.

    • MemberPlanChanged: Triggers when a member changes their plan.

Mapping Plans to Access Levels

  • Each Mighty plan must be mapped to an access level in Member Kitchens. This mapping is essential for granting the correct access to members based on their purchases.

  • You can add plan IDs manually or they will appear automatically after the first webhook event.

  • You can also set optional trial days (0-30). A value of 0 means no trial period.

Understanding Lifecycle Events

Here’s what each lifecycle event does:

  • MemberPurchased: Grants access to the mapped access level and creates a new member if they do not already exist.

  • MemberSubscriptionRenewed: Keeps access active and converts a trial to a full subscription.

  • MemberSubscriptionCanceled: If the cancellation is for a future date, access remains until that date. If the cancellation is immediate, access is revoked right away.

  • MemberRemovedFromPlan: Ends access immediately, regardless of any future periods.

  • MemberPlanChanged: Grants access to the new plan and removes access from the old plan.

Optional Admin API Connection

If you have a Mighty Scale plan or higher, you can connect the Admin API for additional features:

  1. Create an Admin API key in Mighty Networks and copy your network ID.

  2. Paste both the network ID and API key in the Mighty Networks integration settings in App Station.

  3. Test the connection and connect the API.

  4. You can now refresh plans and sync tags and badges.

Tip: Monitor your API requests this month to ensure you stay within the 5,000 request limit included with the Scale plan.

Supported Outbound Events

The integration supports the following outbound events:

Event key

Label

user.signed_up

User signed up

user.email.changed

User email changed

checkout.completed

Checkout completed

subscription.started

Subscription started

subscription.canceled

Subscription cancelled

subscription.ended

Subscription ended

subscription.completed

Subscription completed

subscription.paused

Subscription paused

subscription.resumed

Subscription resumed

access.granted

Access granted

access.revoked

Access revoked

access.expired

Access expired

growth.checkout_abandoned

Checkout abandoned

gamification.badge.awarded

Badge awarded

Webhook Security and Idempotency

  • The bearer key is securely generated and must be included in the header of each request to ensure proper authentication.

  • Duplicate events are handled gracefully, ensuring that your integration remains efficient and error-free.

Disconnecting the Integration

If you need to disconnect the Admin API, it will remove the key and stop tag sync. Disconnecting the entire integration will remove all mappings and settings associated with it.

Did this answer your question?