Configure the Lambda Suite Store integration

Ryan Knuth
Ryan Knuth
  • Updated

To configure the Lambda Suite Store integration, complete the following steps:

  1. In Wicket, navigate to the Settings page (/admin/settings) and click “Integrations”
    wicket-admin-settings-menu.png

  2. The Lambda Suite Store Integration is displayed with a status of “New”
    wicket-admin-integrations-list.png

  3. Click “Edit configuration” for Lambda Suite Store. You'll be taken to the configuration screen.

  4. To enable the integration, select “Yes” for the Enabled field.
    wicket-admin-lambda-enable.png

  5. Select the data synchronization flows desired for the integration
    wicket-admin-lambda-syncflows.png

  6. Select the fields to be synchronized in the Inbound and Outbound flows
    wicket-admin-lambda-syncfields.png

  7. Configure the Membership Mapping Non-Member Group ID.

    This ID relates to the group you have configured in Lambda Suite Store for non-members.
    wicket-admin-lambda-mapping-non-member.png
  8. Configure the mapping between Wicket Membership Tiers and the Lambda Suite Store Groups.

    Select the Wicket Membership Tier to map from the dropdown. The Wicket Membership Tiers are pulled form those configured within your Wicket instance.
    wicket-admin-lambda-mapping-tier.png

    Enter the Lambda Group ID you'd like to map your chosen Wicket Membership Tier to.
    wicket-admin-lambda-mapping-tier-selected.png

    Repeat the above process to add as many mappings as you require.
  9. Enter your Lambda Suite Store Credentials

    Lambda should provide you these credentials before setting up the integration:
    • Lambda Suite Store Base URL
    • Lambda Store Code
    • API Key

    The Lambda Admin Code is the last part of the admin URL for the Lambda Suite Store and it should start with “admin_”.

    wicket-admin-lambda-apicreds-token.png
  10. Click "Save"

    If your API Credentials are correct your settings will be saved and you’ll receive a success notification.

    If your API Credentials are incorrect you’ll receive an error message. Please correct your API Credentials and try again.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.