Attributes are a great way to attach more data to your users, companies, conversations or to store temporary data to build out complex Workflows.

In Intercom there are 5 types of attributes:

These used to store data about users and leads in Intercom. By default, Intercom comes with some basic attributes such as name, phone number, email, etc. You can also add your own custom data attributes depending on the needs of your business. Examples include:

Similar to people data attributes, company attributes are used to provide more data about the companies your business deals with via Intercom. Some default attributes include company name, industry, company website and ID. You can always create more custom attributes, for example:

These are great for storing data about the ticket or conversation that your support team is working on, whether that is to give more context on a customer's issue or for categorization and reporting purposes. Examples of conversation/ticket data attributes include:

Workflows and Fin Tasks can use a new type of attribute called a "temporary attribute". This feature is currently in beta.

Temporary attributes are useful when you need data only for the current workflow and don't want to save it permanently in Intercom for reporting or other purposes. You can create these attributes to hold information that's relevant to the specific workflow being executed.

For example you can create a temporary attribute to:

You can set up Fin Tasks and ask Fin to use any people, company, conversation or ticket attributes by inserting these attributes into the “Task goal and guidance” using the attribute inserter {..}

From this menu, you can pick different types of attributes listed under the different category headers:

Here, you can also set up temporary attributes via the “Results” tab when configuring a Fin Task. These are used to tell Fin what data to output from the task.

For example, you might instruct Fin to classify a user's query and save this as a temporary data attribute.

If you wish to collect data and store it for the user, company, conversation or just temporarily in your Workflow or Fin Task, you can do so by using the “Collect data” step. This is useful if you want to later use the collected data to create conditional logic in the Workflow / Fin Task using branching.

Here, you can specify what type of data attribute you would like to collect.

Actions can retrieve or update data in an external system using data attributes. For example, they can update or fetch user records from your database.

Data attributes can be used in both the request URL and the Request Body of the Action inserting them using the attribute inserter {..}

You also might want to send Fin Task outputs or collected temporary data to an external API for processing and to do so, you need to first create a mapping.

In your Action, you'll need to create the same attribute(s) (contact reason in this example) that exist in your Workflow configuration:

Next, map the action inputs in your Workflow / Fin Task.

Here, for each of your attributes, you can insert the temporary data attribute that is either outputted by Fin performing a task or collected from the user in a Workflow.