|
1 | 1 | ---
|
2 |
| -title: 'Canny-Functions Destination' |
3 |
| -hidden: true |
4 |
| -beta: true |
| 2 | +title: Canny (Actions) Destination |
| 3 | +id: <integration_id> |
| 4 | +--- |
| 5 | + |
| 6 | +{% include content/plan-grid.md name="actions" %} |
| 7 | + |
| 8 | +[Canny](https://canny.io?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is a single place for all customer feedback. It saves you time managing all the feedback while keeping your customers in the loop. Let your customers post and vote on feedback from within your website or mobile app. You'll get an organized list of feedback that you can use to inform your roadmap. |
| 9 | + |
| 10 | +This destination is maintained by Canny. For any issues with the destination, [contact the Canny Support team ](mailto:[email protected]). |
| 11 | + |
| 12 | +{% include content/ajs-upgrade.md %} |
| 13 | + |
| 14 | +## Getting started |
| 15 | + |
| 16 | +1. Go to your [Canny Admin Segment Settings](https://canny.io/redirect?to=%2Fadmin%2Fsettings%2Fsegment). |
| 17 | +2. Obtain your API key by installing the integration. |
| 18 | +3. From the Segment web app, click **Catalog**, then click **Destinations**. |
| 19 | +4. Find the Destinations Actions item in the left navigation, and click it. |
| 20 | +5. Click **Configure Canny (Actions)**. |
| 21 | +6. Select an existing Source to connect to Canny (Actions). |
| 22 | +7. After you finished configuring the destination, update the API key in the Canny (Actions) destination settings, enable destination and save changes. |
| 23 | + |
| 24 | +{% include components/actions-fields.html %} |
| 25 | + |
| 26 | +## Identify |
| 27 | + |
| 28 | +If you haven't had a chance to review spec, take a look to understand what the Identify method does. An example call would look like: |
| 29 | + |
| 30 | +```js |
| 31 | +analytics.identify("userId123", { |
| 32 | + |
| 33 | + name: "John Doe", |
| 34 | +}); |
| 35 | +``` |
| 36 | + |
| 37 | +Identify calls will be sent to Canny as an identify event. Once identified, users will appear in Canny and will appear in your vote-on-behalf feature. The `name` and `email` traits are **required** fields. |
| 38 | + |
| 39 | +## Group |
| 40 | + |
| 41 | +An example call would look like: |
| 42 | + |
| 43 | +```js |
| 44 | +analytics.group("0e8c78ea9d97a7b8185e8632", { |
| 45 | + name: "X Corp", |
| 46 | +}); |
| 47 | +``` |
| 48 | + |
| 49 | +Group calls will be sent to Canny as an group event. Once sent, groups will appear in Canny as companies attached to users. The `name` trait is a **required** field. |
| 50 | + |
| 51 | +### Custom Fields |
| 52 | + |
| 53 | +Custom Fields is a list of [traits](/docs/connections/spec/identify/#traits) to be imported as custom fields for Identify events. |
| 54 | + |
5 | 55 | ---
|
0 commit comments