You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/sources/catalog/cloud-apps/intercom/index.md
+22-24Lines changed: 22 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,32 +18,33 @@ Take your company's email analysis to the next level by **adding Intercom as a S
18
18
3. OAuth into Intercom
19
19
20
20
21
-
4. We will verify all the required permissions
21
+
1. Segment verifies the required permissions
22
22
23
23
24
-
5. Configure the name for the Intercom schema in your warehouse
24
+
1. Configure the name for the Intercom schema in your warehouse
25
25
26
26
27
-
6. Add a warehouse or connect Intercom to an already existing warehouse in your workspace
27
+
1. Add a warehouse or connect Intercom to an already existing warehouse in your workspace
28
28
29
29
30
-
Voila! We'll begin syncing your Intercom data into Segment momentarily, and it will be written to your warehouse at your next Warehouse run.
30
+
Segment begins to sync your Intercom data into Segment, and writes it to your warehouse at your next Warehouse run.
31
+
32
+
31
33
32
34
## Components
33
35
34
36
### Sync
35
37
36
-
Our Intercom source has a sync component, which means we'll make requests to [their API](https://developers.intercom.io/docs/) on your behalf on a 3 hour interval to pull the latest data into Segment. In the initial sync, we'll grab all the Intercom objects (and their corresponding properties) according to the collections table below. The objects will be written into a designated schema corresponding to the source instance's schema name you designated upon creation. For example, if you went with `intercom_prod`, the `users` collection will be accessible at `intercom_prod.users` in SQL.
38
+
The Intercom source has a sync component, which means Segment make requests to [their API](https://developers.intercom.io/docs/) on your behalf on a 3 hour interval to pull the latest data into Segment. In the initial sync, Segment grabs all the Intercom objects (and their corresponding properties) according to the collections table below. The objects will be written into a designated schema corresponding to the source instance's schema name you designated upon creation. For example, if you went with `intercom_prod`, the `users` collection will be accessible at `intercom_prod.users` in SQL.
37
39
38
-
Our sync component uses an upsert API, so the data in your warehouse loaded using sync will reflect the latest state of the corresponding resource in Intercom. For example, if the `users.last_seen_ip` will be the latest value upon each sync.
40
+
The sync component uses an upsert API, so the data in your warehouse loaded using sync will reflect the latest state of the corresponding resource in Intercom. For example, if the `users.last_seen_ip` will be the latest value upon each sync.
39
41
40
-
The source syncs and warehouse syncs are independent processes. Source runs pull your data into the Segment Hub, and warehouse runs flush that data to your warehouse. Sources will sync with Segment every 3 hours. Depending on your Warehouses plan, we will push the Source data to your warehouse on the interval associated with your billing plan.
42
+
The source syncs and warehouse syncs are independent processes. Source runs pull your data into the Segment Hub, and warehouse runs flush that data to your warehouse. Sources will sync with Segment every 3 hours. Depending on your Warehouses plan, Segment pushes the Source data to your warehouse on the interval associated with your billing plan.
41
43
42
-
At the moment, we don't support filtering which objects or properties get synced. If you're interested in this feature, [let us know](https://segment.com/help/contact/)!
43
44
44
45
## Collections
45
46
46
-
Collections are the groupings of resources we pull from your source. In your warehouse, each collection gets its own table.
47
+
Collections are the groupings of resources Segment pulls from your source. In your warehouse, each collection gets its own table.
47
48
48
49
49
50
| Collection | Type | Description |
@@ -102,9 +103,6 @@ Collections are the groupings of resources we pull from your source. In your war
102
103
| monthly_spend | How much revenue the company generates for your business |
103
104
| user_count | The number of users in the company |
104
105
| plan | The name of the plan you have associated with the company |
105
-
| size | The number of employees in the company |
106
-
| website | The URL for the company website |
107
-
| industry | The industry that the company operates in |
108
106
109
107
## Contacts
110
108
@@ -152,7 +150,6 @@ Collections are the groupings of resources we pull from your source. In your war
152
150
| created_at | The time the conversation was created |
153
151
| updated_at | The last time the conversation was updated |
154
152
| message | The message that started the conversation rendered for presentation |
155
-
| user | The user the conversation concerns |
156
153
| assignee | The admin the conversation is currently assigned to. Note `nobody_admin` indicates the conversation is assigned to Nobody |
157
154
| open | Indicates whether a conversation is open (true) or closed (false) |
158
155
| read | Indicates whether a conversation has been read |
@@ -162,21 +159,22 @@ Collections are the groupings of resources we pull from your source. In your war
0 commit comments