Support
Write to support@getrulebook.com. A person answers within 2 business days. This page also tells your admin how to connect each tool, which permissions Rulebook asks for, and why.
Contact us
- Email: support@getrulebook.com.
- Response time: within 2 business days.
- Tell us the tool, the time and what you saw. Do not send passwords, keys or access tokens.
- For a security issue, write to the same address. The security page tells how we protect your data.
The privacy policy tells which data Rulebook keeps and who processes it. The terms of service apply to each use of Rulebook.
Before you connect a tool
- An admin of your company connects Slack, HubSpot, Salesforce and Notion for the whole company. An owner or an admin also connects one Google account for the whole company: Rulebook sends the approved emails from this account.
- In Rulebook, open Connections. Each tool has a Connect button and a Disconnect button. For Slack, HubSpot, Salesforce and Notion, an admin also gets a Check now button.
- Rulebook acts with the access that your admin gives the Rulebook connection. It asks only for the permissions that the work needs.
- You can remove the access of Rulebook in each tool at any time. The integrations page lists what works today.
Google (Gmail, Drive, Docs and Slides)
- An owner or an admin opens Connections in Rulebook and clicks Connect for Google.
- Select the Google account that sends the emails of your company.
- Read the permissions on the Google screen, then click Allow.
- Back in Rulebook, the card shows the email address of the account.
Permissions and why:
- Your email address (
openid,email): to show which account is connected. - Send email (
gmail.send): to send the emails that a person approved, from the connected account. Rulebook does not read the mailbox. - Only the Drive files that you use with Rulebook (
drive.file): to make and update the Docs and Slides of a work item. Rulebook opens only the files that it made or that you selected.
If your company uses Google Workspace, your Workspace admin can need to mark Rulebook as trusted first: Admin console, Security, Access and data control, API controls.
Slack
- A Slack admin clicks Connect for Slack in Rulebook, or uses the Add to Slack link that we send.
- Select your workspace, read the permissions, then click Allow.
- Tell us the channels where your team asks for work. Rulebook reads only these channels and its direct messages.
- In each of these channels, type
/invite @Rulebook.
Permissions and why:
- Send messages (
chat:write): to send approval cards and the status of the work. - Start direct messages (
im:write): to open a direct message with the owner of a work item. - Read its direct messages (
im:history): to get the requests that people send to Rulebook. - Read the channels where an admin added it (
channels:history,groups:history): to turn requests into work items. Rulebook does not read the other channels. - See people and their email addresses (
users:read,users:read.email): to match a Slack user with the same person in your CRM and in Rulebook. - Slash command (
commands): to send the meeting bot to a call with/notetaker. - See the members of public channels (
channels:read): to know who is in a request channel. Rulebook checks this at most once an hour.
HubSpot
- A HubSpot admin clicks Connect for HubSpot in Rulebook.
- Select the HubSpot account of your company.
- Read the permissions, then click Connect app.
- Back in Rulebook, click Check now. The card shows the ID of your HubSpot account.
Permissions and why:
- Read and update deals (
crm.objects.deals.read,crm.objects.deals.write): to find the deal of a work item and, after a person approves, update its fields. Rulebook reads each changed field again to prove the change. - Read contacts and companies (
crm.objects.contacts.read,crm.objects.companies.read): to match the people and companies of a meeting with your records. - Read quotes and line items (
crm.objects.quotes.read,crm.objects.line_items.read): to compare a purchase order with its quote. - Basic access (
oauth): HubSpot needs it for each connected app.
Salesforce
- A Salesforce admin opens Connections in Rulebook.
- Type the Salesforce login address. Leave it empty for login.salesforce.com. A company with My Domain or a sandbox types its own address.
- Click Connect, sign in to Salesforce, read the permissions, then click Allow.
- Back in Rulebook, click Check now. The card shows the ID of your Salesforce org.
Permissions and why:
- Access your data with the API (
api): to read opportunities, accounts, contacts and quotes, and, after a person approves, to update opportunity fields, create tasks and add notes. Rulebook reads each record again to prove the change. - Keep the connection (
refresh_token): to do approved work, for example a scheduled renewal check, without a new sign-in each time.
Salesforce lets users connect only to apps that are installed in the org or that an admin approved. For a pilot, we help your admin set up the Rulebook app in your org first. Write to support@getrulebook.com.
In development
Notion
The Notion connection is in development and is not available to customers yet. When it is ready, a Notion admin clicks Connect for Notion in Rulebook, selects the pages to share with Rulebook, then clicks Allow access.
Permissions and why:
- Read content: to read the pages that you share with Rulebook, for example your sales process. Rulebook does not see the other pages.
- Update and insert content: to make the changes to your shared pages that a person approved.
- Rulebook does not ask for the email addresses of your Notion users.
If a connection stops
- The Connections page shows "Reconnect needed" and the reason. Click Reconnect to continue.
- Rulebook checks each company connection every hour. When one needs a reconnect, Rulebook tells the person who connected it.
- If the problem stays, write to support@getrulebook.com. We answer within 2 business days.
Rulebook is in early development. We start pilots with a small number of teams. Join the waitlist