Stacker
Login to StackerStart buildingChangelogFeedbackStacker Classic Docs
  • Getting Started
    • How Stacker Works
    • Introduction to Editing Data
      • Stacker Tables: Paste Data
      • Stacker Tables: Import a CSV
    • Introduction to Designing your app
    • Introduction to Adding Users & Permissions
    • Introduction to Portals
  • Workspace, Portals, and Apps
    • Overview
    • Workspace
      • Workspace Settings
      • Workspace Users
      • Groups
    • Portals
      • Custom Domain
    • Apps
  • AI & Automations
    • AI Agents
      • Setting up your AI agent
        • AI Agent persistent conversation IDs
      • Agent Triggers
      • Operating Instructions
      • Tools
      • Skills
      • Renderer
      • History and Tasks
    • Workflows (Beta)
    • Integrations
      • Zapier Integration
      • Make.com Integration
    • Open API Overview
      • Setup Guide
      • Authentication
      • Additional Headers
      • Field API names
      • Accounts, Stacks, Objects, Fields
      • Record Actions
    • Action buttons
      • Use an Action Button
      • Create a page button on detail layout
      • Action buttons in field widgets
      • Edit an action button
  • Data management
    • Import data to Stacker Tables
      • Stacker Tables: Import a CSV
        • External IDs
      • Stacker Tables: Paste Data
    • Edit your Data in the Data Grid
      • Structuring data/schema
      • Add new fields
      • Formula Field
      • Creating and Editing Data
      • Share data with other apps
      • Linking your data
      • Set field default values from the data grid
    • Edit Data in the Layout
    • Layout Types
    • Data Integrations (Beta)
      • Airtable (Beta)
      • Hubspot (Beta)
      • Intercom (Beta)
      • Gorgias (Beta)
      • Netsuite (Beta)
  • User Access
    • Add Users
      • Roles
    • Log in flow
  • Customize Layouts
    • List Layout
      • Display Types
      • Edit List Layouts
    • Detail Layout
      • Layout options
      • Tabs
        • Feed Tab
      • Page Buttons
      • Widgets
      • Customize fields
        • Field Icons
    • Detail Pages (new! beta)
      • Widgets
      • Headers
      • Style
      • Controls
      • Layout Options
    • Create form
      • Auto-filling values into create forms
    • Custom Pages
    • Navigation
  • Security
    • Roles
    • Add User Permissions
      • Create or edit a permission rule
        • Record Filter
        • Ownership filter
        • Data filter
        • Permission Sharing
        • Field Access
        • Record Deletion
      • Troubleshooting Permissions
    • Data Filters
      • Conditional Visibility Filter
  • Interactivity
    • Feeds
    • Mobile Responsiveness
  • Use Cases
    • Profile views and team directories
    • Create a Ticketing App
    • Create a CRM App
  • Account Information
    • Stacker Support Access
    • Pricing
Powered by GitBook
On this page
  • Persistent AI Agent Conversations
  • How to set up on detail pages:
  • Tool usage for Persistent IDs:
  1. AI & Automations
  2. AI Agents
  3. Setting up your AI agent

AI Agent persistent conversation IDs

Maintain your agent even when you click away from a record or to keep consistency across teams.

PreviousSetting up your AI agentNextAgent Triggers

Last updated 1 day ago

Persistent AI Agent Conversations

Create long-running conversations around a single record, task or topic by giving the conversation a unique thread ID. Multiple triggers can then send events into that same conversation thread, allowing your agent to responds to each event with all the context and plans it had previously. Use the thread in detail page widgets to give access to a persistent conversation, scoped to a particular record, user, or anything else you want.

How to set up on detail pages:

  1. Add an AI agent widget to your detail page

  2. Set your template ID to keep it persistent based on record ID, user ID, or something else:

    1. Record ID use {record.id}: this will keep the conversation the same based on the record regardless of the user logged in.

    2. User Record use {record.user}: this will keep the conversations or other AI tasks based on the user logged in.

    3. Other fields use {record.customer.primary_contact.email}

      1. The path values here correspond to what is shown for the ‘developer name’ in the Manage Fields modal.

      2. If it is a multi-link, we will use only the first record in the list.

Tool usage for Persistent IDs:

You can also use the ID for emails and conversations that come through your AI agent.

  1. Set the ID on your Send an email tool by setting a Thread ID:

  1. Use the Record Creation trigger along with a Conversation ID set to connect with specific users or other conversation records.

For example, when adding new records that associate with the same company, using the {record.company} will help the AI agent reference all record information that is in common with the company. Helping your AI agent gather more accurate and complete information.