What are attributes?
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:
People attributes
Company attributes
Conversation attributes
Ticket attributes
Temporary attributes
[NEW]
Note: Fin Tasks are a legacy feature. Since March 12th, 2026, you can't create new Tasks, and all new builds are created as Fin Procedures. Your existing Tasks remain fully supported and read and update attributes the same way.
What types of attributes exist?
People data 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:
Tier or plan that the user is on
Last invoice amount
Last item purchased
Company data attributes
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:
Company tax/VAT ID
Number of employees
Whether a company is a subsidiary or not
Conversation/ticket data attributes
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.
This data can be populated in three primary ways:
Manually by a teammate in the Inbox.
Through Workflows, using the "Collect data" step.
Automatically by the Fin AI Agent, using Fin Attributes.
Examples of conversation/ticket data attributes include:
Category or reason for customer query
Product customer is contacting about
Follow up needed (true / false)
Conversation ID is available as a conversation attribute that can be accessed in:
Workflows (search "Conversation ID")
Tasks (search "Conversation ID")
Procedures (via Read attribute → Conversation ID)
This enables you to use Conversation ID for:
Workflow tracking and conversation referencing.
Data integration with external systems.
Enhanced reporting and analytics capabilities.
Better customer support with conversation references.
Automatically classify conversations with Fin Attributes
Fin Attributes automatically classifies every conversation by detecting attributes like issue type, urgency, or sentiment. Conversations are instantly classified, which allows you to trigger workflows, route conversations to the right team, and generate accurate reports without any manual effort.
Tip: While this article covers the basics of what conversation attributes are, we highly recommend reading the full Fin Attributes article to learn how to set up and use AI-powered classification.
Temporary attributes [NEW]
Fin Procedures and Workflows can use a new type of attribute called a "temporary attribute".
Temporary attributes are useful when you need data only for the current Procedure or Workflow run 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 that specific run.
For example you can create a temporary attribute to:
Capture a customer's selected booking ID
Customer’s preferred delivery date
Ask Fin to classify user query or collect some data
Where can attributes be used?
Fin Procedures
Add attributes to an Instruction step in your Fin Procedure by typing "@" in line with your text instructions. Choose Read attribute to have Fin use existing data, or Update attribute to have Fin save a new value. You can use any people, company, conversation, or temporary attribute. See Building Fin Procedures.
Temporary attributes are useful when you need data only for the current Procedure run and don't want to save it permanently in Intercom for reporting or other purposes. To create one:
In an Instruction step, type "@" and select Update attribute.
Click Create attribute.
Choose a Format, enter a Name and a Description, then click Create and insert.
For example, you might instruct Fin to classify a customer's question and save the result in a temporary attribute.
Temporary attributes can also be used outside Instruction steps, such as in a Condition step to branch, or in a note added with @Add note.
Collecting data in a Procedure or Workflow
To collect data and store it for the person, company, conversation, or temporarily in a Fin Procedure, write it into an Instruction step. For example: "Ask the customer for their order number, then @Update attribute to save it." You can then add a Condition step to branch on the saved value. In a Workflow, use the Collect data step instead. This is useful if you want to use the collected data later to create conditional logic with branching. The two screenshots below show the Collect data step in a Workflow.
Here, you can specify what type of data attribute you would like to collect.
Data connectors
Data connectors can retrieve or update data in an external system using data attributes. For example, they can update or fetch user records from your database.
Attributes can be used in both the request URL and the Request Body of the Data connector, inserting them using the attribute inserter {..}
In a Procedure
Add a data connector to an Instruction step by typing "@" and selecting Call data connector. You don't need to map inputs or outputs. Fin works out which inputs the connector needs from its configuration, and you can read the response in later steps with @Read attribute (for example, Get orders > status).
Connector responses are available only inside the Procedure. They don't appear as conversation attributes in the Inbox. To save a response to a conversation attribute, use Handoff to workflow and set the attribute in the Workflow. The Procedure does not resume after that handoff. For common problems, see Troubleshooting Fin Procedures and Data connectors.
In a Workflow
You also might want to send Workflow outputs or collected temporary data to an external API for processing and to do so, you need to first create a mapping.
In your Data connector, 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.
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.
When a Workflow branch checks a company attribute (such as built date), Intercom evaluates the condition against every company the contact belongs to. If any company meets the condition, the branch will match and proceed accordingly.
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts





