Configuring Profile sync between Wicket and Pheedloop

Ryan Knuth
Ryan Knuth
  • Updated

Activation

To configure the Wicket and Pheedloop integration, it first needs to be activated. Activate the integration following these steps:

  1. In Wicket, navigate to the settings page (/admin/settings) and click "Integrations"
    wicket-admin-settings-links.png

  2. The Pheedloop Integration is displayed with a status of “New”
    wicket-admin-settings-integrations.png

  3. Click “Edit configuration” for the Pheedloop integration

    wicket-admin-pheedloop-config-options.png

  4. For the “Enabled” field select “Yes”
    wicket-admin-pheedloop-enabled.png

  5. Select the data synchronization scenarios desired for the integration
    wicket-admin-pheedloop-sync-flows.png

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

  7. Choose the Person roles to synchronize with the Outbound scenario. If no roles are specified, all person records in Wicket will be synchronized.
    wicket-admin-pheedloop-sync-roles.png

  8. Retrieve and enter your Pheedloop API key

    You can find your Pheedloop API key by logging into your Pheedloop account and opening one of your existing events, or creating a new one.

    In the event’s left menu, scroll to the bottom and click “Advanced Functions”

    pheedloop-event-nav-adv-features-link.png

    Click the "Integrations" tab at the top of the page.
    pheedloop-integrations-apikeys.png

    Copy the API key value from Pheedloop, and paste it into the API Key field in the Pheedloop configuration page in Wicket.
    wicket-admin-pheedloop-apikey.png

  9. When you're satisfied with your settings, click "Save." Your configuration is now completed.

    Note: If the API key is correct the integration settings will be saved. If Wicket returns an error, verify the API key value you entered is the same as the API key value in Pheedloop.

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.