During our live session, we will install Momentum in three easy steps. The process is quick and generally takes less than 15 minutes! We've listed details about the systems access you’ll need and the changes we’ll be applying so there are no surprises during our installation session. Once the process is complete, your team will be ready to use Momentum.

This document has a lot of detail for those interested in diving in. In case you want to show up prepared for our call, all you need to know is that we'll need the following 2 admin privileges to install:

  • Slack system administrator permissions

  • Salesforce system administrator permissions


System changes we’ll apply

✅ Step 1: Installing the Momentum Salesforce package

What does the installation do?

Momentum’s Salesforce package will be installed in your instance. This package receives triggers upon key CRM events like new Leads, Tasks, or Opportunities being created or updated. Once received (and only if the event is relevant based on your configuration), our package will post the update to our cloud service.

Why do you need to do it?

By sending important change events directly from your Salesforce instance into our cloud service, this package allows us to stay on top of crucial Object updates without polling your Salesforce instance regularly, reducing the number of API requests needed by our service to run.

Warnings and considerations

This package will run under the read access of the administrator that triggered the installation. Although we’ve been battle-testing the mechanisms in this package over time, it’s essential to keep an eye on error reports to stay on top of any conflicting packages or configurations your instance may exhibit.

✅ Step 2: Installing the Momentum Slack app

What does the installation do?

Momentum will access specific Slack permissions like posting messages or inviting participants to channels. The app will show up as a Slack app for your whole team to interact with, but it won’t proactively contact any of your team members on its own.

Why do you need to do it?

Momentum’s main interactions and workflows are built on top of Slack. Our Slack app is fundamental to delivering a top-of-the-line experience to the members of your team who will be taking advantage of Momentum to close deals.

Warnings and considerations

Momentum won’t be reading messages and history from any channels it’s not invited to. Momentum doesn’t need to be invited to specific channels to work well.

✅ Step 3: Granting Momentum access to Salesforce

What does the installation do?

Granting Momentum access will let it bootstrap its configuration. We’ll read the list of Salesforce users in your organization, the list of stages and custom fields in your Opportunities, and other foundational settings that allow Momentum to read and write into Salesforce.

Why do you need to do it?

One of Momentum’s core value propositions is its ability to post Opportunities, Leads, Quotes, and Tasks directly in Slack. Additionally, your team members can update or even create these objects without ever stepping into Salesforce. Allowing Momentum to understand the types of fields your objects have is fundamental to let users read and write these from Momentum.

Warnings and considerations

Users, fields, custom objects, and other settings are read upon initial installation. Other administrative tasks that require us to read these and refresh Momentum’s local configuration will continue to execute during the regular operation of the product.

Did this answer your question?