1
1
---
2
2
title : Attio (Actions) Destination
3
3
hide-boilerplate : true
4
+ id : 64c031541451bb784943f809
5
+ beta : true
6
+ hidden : true
4
7
---
5
8
6
9
{% include content/plan-grid.md name="actions" %}
7
10
8
- Powerful, flexible and data-driven, [ Attio] ( https://attio.com ) makes it easy to build the
11
+ Powerful, flexible and data-driven, [ Attio] ( https://attio.com ) { : target =" _ blank”} makes it easy to build the
9
12
exact CRM that your business needs.
10
13
11
14
This destination allows you to use your existing Segment events to create or update
12
- records in Attio, for example creating User records from identify events.
15
+ records in Attio, for example creating Attio User records from Segment Identify events.
13
16
14
17
## Getting started
15
18
@@ -40,7 +43,7 @@ Person.
40
43
41
44
> info ""
42
45
> To use the User standard object, you'll need to make sure it's activated first. Visit
43
- > your [ Workspace Settings > Objects] ( https://app.attio.com/_/settings/data/objects ) page
46
+ > your [ Workspace Settings > Objects] ( https://app.attio.com/_/settings/data/objects ) { : target =" _ blank”} page
44
47
> and click the "Activate" button next to the Users object.
45
48
46
49
This mapping makes the assumption that your Segment event includes two properties:
@@ -50,7 +53,7 @@ This mapping makes the assumption that your Segment event includes two propertie
50
53
51
54
You can specify additional attributes to be mapped on the ** Edit Mapping** page.
52
55
53
- For example, we could set some additional properties on the Person using these Mapping
56
+ For example, you could set some additional properties on the Person using these Mapping
54
57
Fields under "Additional Person attributes". The column on the left should contain
55
58
properties from your event, or custom text, and the column on the right should reference
56
59
attributes on that object type in Attio, represented by their slug.
@@ -104,7 +107,7 @@ This mapping makes the assumption that your Segment event includes two propertie
104
107
105
108
You can specify additional attributes to be mapped on the ** Edit Mapping** page.
106
109
107
- For example, we could set some additional properties on the Company using these Mapping
110
+ For example, you could set some additional properties on the Company using these Mapping
108
111
Fields under "Additional Company attributes". The column on the left should contain
109
112
properties from your event, or custom text, and the column on the right should reference
110
113
attributes on that object type in Attio, represented by their slug. For example:
@@ -123,7 +126,7 @@ Create or update a single type of Object, given a matching attribute name and va
123
126
example, you could assert that a Company exists using a given ` domain ` property.
124
127
125
128
This mapping makes the assumption that your data includes the matching property. For the
126
- following example, we'll assume you have domain and twitter properties, like so:
129
+ following example, assume you have domain and twitter properties, like so:
127
130
128
131
``` json
129
132
{
@@ -135,13 +138,13 @@ following example, we'll assume you have domain and twitter properties, like so:
135
138
}
136
139
```
137
140
138
- First, we 'll need to set the "Attio Object" property - it should pre-populate with all of
139
- the activated objects in your Attio instance. Then, we 'll need to set the "Matching
141
+ First, you 'll need to set the "Attio Object" property - it should pre-populate with all of
142
+ the activated objects in your Attio instance. Then, you 'll need to set the "Matching
140
143
Attribute" property. This is the slug for the attribute in Attio, and must also be present
141
- in your "Attributes" mapping in the next form. In this example, we 'll select "Company" as
144
+ in your "Attributes" mapping in the next form. In this example, you 'll select "Company" as
142
145
the Attio Object, and "domains" as the Matching Attribute.
143
146
144
- We would then need to ensure the Attributes mapping is populated like so:
147
+ You would then need to ensure the Attributes mapping is populated like so:
145
148
146
149
| Select event variable | Enter key name |
147
150
| -----------------------------------------| ----------------|
0 commit comments