The intercom API reference.
https://api.intercom.io/
https://api.eu.intercom.io/
https://api.au.intercom.io/
With the AI Content APIs, you can create and manage External Pages and Content Import Sources for your Fin Content Library.
External Pages are pages that you want Fin to be able to answer questions about. The API for External Pages is a great way to ingest into your Fin Content Library pages that are not publicly accessible and hence can't be crawled by Intercom.
Content Import Sources are the sources of those pages, and they are used to determine the default audience for the pages (configured via the UI). You should create a Content Import Source for each source of External Pages that you want to ingest into your Fin Content Library.
You can then iterate through the content from that source via its API and POST it to the External Pages endpoint. That endpoint has an external_id parameter which allows you to specify the identifier from the source. The endpoint will then either create a new External Page or update an existing one as appropriate.",
Everything about your Custom Object instances.
From now on, to access this endpoint, you need additional permissions. Please head over to the Developer Hub app package authentication settings to configure the required permissions.
You can add an Content Import Source to your Fin Content Library.
If you intend to create or update External Pages via the API, this should be set to api.
The status of the content import source.
{ "sync_behavior": "api", "status": "active", "url": "https://help.example.com" }
Conversations are how you can communicate with users in Intercom. They are created when a contact replies to an outbound message, or when one admin directly sends a message to a single contact.
{ "from": { "type": "user", "id": "536e564f316c83104c000020" }, "body": "Hello", "created_at": 1671028894 }
Array of objects representing the options of the list, with value as the key and the option as the value. At least two options are required.
The model that the data attribute belongs to.
The readable description you see in the UI for the attribute.
{ "data_type": "options", "options": [ { … }, { … } ], "name": "My Data Attribute", "model": "contact", "description": "My Data Attribute Description", "messenger_writable": false }