Skip to main content
All CollectionsGetting started
Salesforce: Permissions needed to integrate with Rattle
Salesforce: Permissions needed to integrate with Rattle

Pre-requisites to get started with Rattle

Gauransh Vaishnav avatar
Written by Gauransh Vaishnav
Updated over 11 months ago

Now that you've decided to use Rattle, here is what you need to check before you get started:

Check your Salesforce edition

To use Rattle, you need to be on the 'Enterprise' edition or above. We currently do not support the 'Professional' edition.

To check this, log in to your Salesforce instance and go to Setup > Company Settings > Company Information. This is where you can see your Salesforce edition.

Required Salesforce permissions

Next, you need to make sure that you've all the necessary permissions in your Salesforce instance to get started.

To check this on your Salesforce instance, go to Setup > Users > Profiles > System Administrator. You should have the following four permissions enabled:

1. Customize Application:

  • Purpose:

    • Create, Edit, and Delete Workflow Rules, Tasks, Field Updates, Outbound Messages

    • Create, Edit, and Delete Custom objects

  • Impact: If disabled, Users won’t be able to create or update workflows and Rattle won’t be able to create custom objects in Salesforce.

  • Affected Rattle features:

    1. On create/update workflows

    2. Time-based workflows

    3. Stage stuck workflows

    4. Approvals

    5. Deal rooms

    6. Enablement workflows

  • Expected error - Error: Operation INSERT cannot be applied on EntityObject of type: ActionOutboundMessage, id: <null> through Tooling API

2. Send Outbound Messages:

This permission needs to be enabled for every user who is creating/editing the record (as their profile acts as a trigger point)

  • Purpose:

    • Allows users to receive Rattle alerts on their Slack or MS Teams

    • Required for triggering of Outbound Message whenever a record is created/updated.

  • Impact: If disabled, Users won’t receive Rattle message.

  • Affected Rattle features:

    1. On create/update workflows

    2. Time-based workflows

    3. Stage stuck workflows

    4. Approvals

    5. Deal rooms

    6. Enablement workflows

3. Manage Flows:

To create Salesforce flows.

  • Purpose: Allows users to create Rattle workflows that utilize (but do not store) SFDC data

  • Impact: If disabled, Users won’t be able to create Rattle workflows and Salesforce Flows.

  • Affected Rattle features:

    1. On create/update workflows

    2. Time-based workflows

    3. Stage stuck workflows

    4. Approvals

    5. Deal rooms

    6. Enablement workflows

4. View all Data:

To activate Salesforce flows.

  • Purpose: Allows users to activate Rattle workflows that utilize (but do not store) SFDC data

  • Impact: If disabled, Users won’t be able to activate Rattle workflows and Salesforce Flows.

  • Affected Rattle features:

    1. On create/update workflows

    2. Time-based workflows

    3. Stage stuck workflows

    4. Approvals

    5. Deal rooms

    6. Enablement workflows

  • Error message (if permission is not given): You can’t activate this flow because it always runs on the system context. Your Salesforce admin can help with that.

5. Modify Metadata (through Metadata API functions):

Provides Rattle with access to SFDC Flows, Workflow rules, and Outbound message creation.

  • Purpose: Rattle needs permission to manage Metadata in Flow, Workflow Rule, and Outbound Message creation.

  • Impact: If disabled, Users won’t be able to create workflows

  • Affected Rattle features:

    1. On create/update workflows

    2. Time-based workflows

    3. Stage stuck workflows

    4. Approvals

    5. Deal rooms

    6. Enablement workflows

Rattle alerts will not fire if these permissions are not enabled for the Super Admin (a.k.a integration user), other Rattle users only need the Send Outbound Messages permission enabled.

Note: You will still be able to integrate with Rattle if you've used the Permission sets method to configure your Salesforce. Just make sure you have the same 5 permissions mentioned above.

Confirm your Salesforce permissions on Rattle

Check if your permissions are enabled on Rattle by navigating to Integrations and hovering over the profile icon next to your Salesforce logo.

With these checks out of the way, you are all set to get started with Rattle 👍

See also

Did this answer your question?