The information contained in this document is confidential, privileged, and only for the use of internal Birdeye users. This document may not be used, published or redistributed.

*This integration is supported for Enterprise businesses.

Integrating Birdeye with Centershift
User Manual

SUPPORT ARTICLE

Introduction

Integration Requirements

Triggers Supported

Integration Process

Curl Command

Create Integration Group (Curl Command)
Fetch information for all the triggers available for Centershift (Curl Command)
Update triggers in Integration Group
Find Business Integration Group Details (Curl Command)
Integration Mapping

Appendix

Campaigns Tags
Restriction Reason

Introduction

Centershift has been a trusted partner offering self-storage management software since 2001. Centershift’s goal is to help self-storage operators increase revenue, become more efficient, and reduce costs. Store Enterprise™ and Store Advantage™ are cloud-based applications that integrate seamlessly with websites, call centers, web aggregators, mobile devices, centralized mail services, corporate offices and other business systems. Centershift’s customer base includes small owners and management firms as well as some of the largest operators in the self-storage industry.

Integration Requirements

Triggers Supported

Birdeye allows you to fetch data from your CRM using some predefined triggers. You can choose any combination from the list of available triggers and inform the support team about your selection. Here are the supported triggers for Centershift

Trigger Name	Trigger Name/ AdditionalParam Value	Trigger Description
Centershift Data Trigger Service	contact trigger	This trigger is used to fetch rental data which are updated in the last 24 hours.

Details required from the Centershift dashboard

Trigger Details

Details required from the Birdeye dashboard

Enterprise Id for multi-location account

Integration Process

Before you can integrate Centershift with Birdeye, you will need to set up the following configurations:

1. Business Integration Group:

A business integration group is a configuration that supports the business hierarchy of individual businesses on the Birdeye platform. The properties that are common for all business integrations are entered at the group level. Setting up a business integration group allows you to associate multiple business locations with the Enterprise account. Below is the list of curl commands that you will need to run to set this up.

Curl Commands

Create Integration Group (Curl Command)

Copy this Curl Command

curl --location --request PUT 'https://common-services.birdeye.com/integration/add/businessintegrationgroup' \
--header 'Content-Type: application/json' \
--data-raw '{
"parentBusinessNumber": 163522891525807,
"integrationSourceId": 107,
"integrationGroupProperties": [
{
"propertyKey": "centershift.password",
"propertyValue": "B!$cu1tsNGr@v4",
"isSecure": false
},
{
"propertyKey": "centershift.username",
"propertyValue": "SS3BirdEye",
"isSecure": false
},
{
"propertyKey": "centershift.channel",
"propertyValue": "21",
"isSecure": false
},
{
"propertyKey": "centershift.orgid",
"propertyValue": "5041",
"isSecure": false
}
],
"integrationGroupTriggers": [
{"triggerId": 122,
"triggerTypeId": 1,
"actionIds": [
1
]
}
]
}'

82134817484848 - Business ID - This is the Enterprise ID for a multi-location account.
122 - Integration Trigger ID - Can be one or more triggers. Ask the client what trigger they would like to integrate with then run the curl command to fetch all possible triggers for Centershift. Identify the trigger Id (s) and insert (use commas) in case of multiple trigger Ids.

Fetch information for all the triggers available for Centershift (Curl Command)

Copy this Curl Command

curl --location --request GET 'https://common-services.birdeye.com/integration/trigger/integrationtriggers/sourceid/107' \
--header 'cache-control: no-cache' \
--header 'content-type: application/json'

Sample response: A sample response like this would appear after you run the curl command. The response will have the trigger name, description and the ID. This trigger Id will be utilized while creating the integration group. An integration can have one or more triggers. To use more than one trigger, enter comma separated values while creating the integration group.

[
{
"id": 117,
"triggerService": "centershiftDataTriggerService",
"displayName": "Centershift Data Trigger Service",
"description": "This trigger is used to fetch customer data which are updated in the last 24 hours",
"active": true,
"integrationTriggerType": {
"id": 1,
"name": "JOB"
},
"actionGroupId": 1,
"sourceIdsList": [
107
],
"triggerName": "Appointment"
}
]

117- Trigger ID

Update triggers in Integration Group (Curl Command)

Copy this Curl Command

curl --location --request POST 'https://common-services.birdeye.com/integration/update/businessintegrationgroup?replaceTriggers=true' \
--header 'cache-control: no-cache' \
--header 'content-type: application/json' \
--data-raw '{
"groupId": 14,
"integrationGroupTriggers": [
{
"triggerId": 117,
"triggerTypeId": 1
}
]
}'

replaceTriggers=true To replace existing trigger(s), enter the value for replaceTriggers as true. To add new trigger(s) to the existing list, the value for replaceTriggers should be false.
14 - The Group Id which was returned in the previous step will be entered here.
117 - Enter the Trigger Id (s) which need to be added or updated to the integration.

Find business integration group details (Curl Command)

Copy this Curl Command

curl --location --request GET 'https://common-services.birdeye.com/integration/businessintegrationgroup/159894373919788' \
--header 'Cache-Control: no-cache'

159894373919788 - Enterprise ID: Enter the Enterprise Id here to get the integration group details for a business.

[
{
"groupId": 19522,
"integrationSourceType": {
"id": 107,
"integrationSource": "CENTERSHIFT",
"sourceCategory": "Real Estate",
"integrationType": "Birdeye API",
"integrationPlan": "Basic",
"oauthEnabled": false},
"integrationGroupTriggers": [
{
"triggerId": 117,
"triggerTypeId": 1,
"actionIds": [
1
]
}
]
}
]

19522 - Group ID: A group Id will be returned in the sample response with the details of the existing triggers for a business.

Integration Mapping

Once the Integration Group is created, the next step is to create the Integration Mapping.

Copy this Curl Command

curl --location --request PUT 'https://common-services.birdeye.com/integration/add/businessintegrationmapping' \
--header 'Content-Type: application/json' \
--data-raw '{
"businessNumber": 163522891525807,
"integrationGroupId": 736,
"integrationProperties": [],
"active": true,
"test": true,
"beta": false
}'

163522891525807 - Enterprise Number: Enter the Enterprise number here.
Note: Please use the same enterprise number that we have used to setup the integration group.
736 - Integration Group ID: Enter the Integration Group Id which was returned when the Integration group was created.
true - Active: Set “true” if you want to enable the integration, else set “false”.

Appendix

Campaigns Tags

Campaign tags are used to set up campaigns within the Birdeye dashboard. These tags are either provided by the client or can be fetched from Kibana for already checkedIn contacts.

Centershift Campaign tags are:
Contact address, Contact active

Restriction Reason

Restriction reason is used to identify the contacts which have been opted-out(restricted) from sending a review request. This reason can be fetched from Kibana for contacts that are checked in already.

Possible restriction reasons for Centershift are: