---
title: "Intercom"
description: "Read and manage permitted Intercom contacts, companies, conversations, articles, tickets and workspace resources using the official REST API pinned to version 2.17. Use an access token from your workspace app with only t"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Intercom

<p>Read and manage permitted Intercom contacts, companies, conversations, articles, tickets and workspace resources using the official REST API pinned to version 2.17. Use an access token from your workspace app with only the required permissions. Creating or replying to messages can contact real users. Lists and searches preserve native pagination without automatic following. This connection uses the default api.intercom.io region; regional EU/Australia origins and unsupported uploads require a separate configuration.</p>

<details data-command-index><summary>What you can do (259)</summary>
<h2>What you can do</h2>
<p>Available commands: 259 (117 read, 142 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-identifyadmin">Identify an admin</a> — <code>intercom.identifyadmin</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getmacro">Retrieve a macro</a> — <code>intercom.getmacro</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listmacros">List all macros</a> — <code>intercom.listmacros</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-setawayadmin">Set an admin to away</a> — <code>intercom.setawayadmin</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listactivitylogs">List all activity logs</a> — <code>intercom.listactivitylogs</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-searchactivitylogs">Search activity logs</a> — <code>intercom.searchactivitylogs</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listactivitylogeventtypes">List all activity log event types</a> — <code>intercom.listactivitylogeventtypes</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listadmins">List all admins</a> — <code>intercom.listadmins</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getofficehoursexception">Retrieve an office hours exception</a> — <code>intercom.getofficehoursexception</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updateofficehoursexception">Update an office hours exception</a> — <code>intercom.updateofficehoursexception</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deleteofficehoursexception">Delete an office hours exception</a> — <code>intercom.deleteofficehoursexception</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listofficehoursexceptions">List all office hours exceptions</a> — <code>intercom.listofficehoursexceptions</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createofficehoursexception">Create an office hours exception</a> — <code>intercom.createofficehoursexception</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getofficehoursschedule">Retrieve an office hours schedule</a> — <code>intercom.getofficehoursschedule</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updateofficehoursschedule">Update an office hours schedule</a> — <code>intercom.updateofficehoursschedule</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deleteofficehoursschedule">Delete an office hours schedule</a> — <code>intercom.deleteofficehoursschedule</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listofficehoursschedules">List all office hours schedules</a> — <code>intercom.listofficehoursschedules</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createofficehoursschedule">Create an office hours schedule</a> — <code>intercom.createofficehoursschedule</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrieveadmin">Retrieve an admin</a> — <code>intercom.retrieveadmin</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-removeadmin">Remove an admin</a> — <code>intercom.removeadmin</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listcontentimportsources">List content import sources</a> — <code>intercom.listcontentimportsources</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createcontentimportsource">Create a content import source</a> — <code>intercom.createcontentimportsource</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deletecontentimportsource">Delete a content import source</a> — <code>intercom.deletecontentimportsource</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getcontentimportsource">Retrieve a content import source</a> — <code>intercom.getcontentimportsource</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatecontentimportsource">Update a content import source</a> — <code>intercom.updatecontentimportsource</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listexternalpages">List external pages</a> — <code>intercom.listexternalpages</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createexternalpage">Create an external page (or update an external page by external ID)</a> — <code>intercom.createexternalpage</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deleteexternalpage">Delete an external page</a> — <code>intercom.deleteexternalpage</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getexternalpage">Retrieve an external page</a> — <code>intercom.getexternalpage</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updateexternalpage">Update an external page</a> — <code>intercom.updateexternalpage</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-attachtagtoexternalpage">Add a tag to an external page</a> — <code>intercom.attachtagtoexternalpage</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-detachtagfromexternalpage">Remove a tag from an external page</a> — <code>intercom.detachtagfromexternalpage</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listarticles">List all articles</a> — <code>intercom.listarticles</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createarticle">Create an article</a> — <code>intercom.createarticle</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievearticle">Retrieve an article</a> — <code>intercom.retrievearticle</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatearticle">Update an article</a> — <code>intercom.updatearticle</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deletearticle">Delete an article</a> — <code>intercom.deletearticle</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievearticledraft">Retrieve an article draft</a> — <code>intercom.retrievearticledraft</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-stagearticledraft">Stage an article draft</a> — <code>intercom.stagearticledraft</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-publisharticledraft">Publish an article draft</a> — <code>intercom.publisharticledraft</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-attachtagtoarticle">Add a tag to an article</a> — <code>intercom.attachtagtoarticle</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-detachtagfromarticle">Remove a tag from an article</a> — <code>intercom.detachtagfromarticle</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listarticleversions">List article versions</a> — <code>intercom.listarticleversions</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievearticleversion">Retrieve an article version</a> — <code>intercom.retrievearticleversion</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-searcharticles">Search for articles</a> — <code>intercom.searcharticles</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listawaystatusreasons">List all away status reasons</a> — <code>intercom.listawaystatusreasons</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listaudiences">List all audiences</a> — <code>intercom.listaudiences</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createaudience">Create an audience</a> — <code>intercom.createaudience</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrieveaudience">Retrieve an audience</a> — <code>intercom.retrieveaudience</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updateaudience">Update an audience</a> — <code>intercom.updateaudience</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deleteaudience">Delete an audience</a> — <code>intercom.deleteaudience</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-post--export-reporting_data-enqueue">Enqueue a new reporting data export job</a> — <code>intercom.post-.export.reporting_data.enqueue</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-get--export-reporting_data--job_identifier-">Get export job status</a> — <code>intercom.get-.export.reporting_data.-job_identifier-</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-get--export-reporting_data-get_datasets">List available datasets and attributes</a> — <code>intercom.get-.export.reporting_data.get_datasets</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-startfinconversation">Start a conversation with Fin</a> — <code>intercom.startfinconversation</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-replytofin">Reply to Fin</a> — <code>intercom.replytofin</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-submitfincsat">Submit a CSAT rating</a> — <code>intercom.submitfincsat</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listfincapabilities">Discover Fin&#39;s capabilities</a> — <code>intercom.listfincapabilities</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-askfin">Ask Fin</a> — <code>intercom.askfin</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-runfinprocedure">Run a Fin procedure</a> — <code>intercom.runfinprocedure</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-escalatefinconversation">Escalate to a human</a> — <code>intercom.escalatefinconversation</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listhelpcenterredirects">List all redirects for a help center</a> — <code>intercom.listhelpcenterredirects</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createhelpcenterredirect">Create a redirect</a> — <code>intercom.createhelpcenterredirect</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievehelpcenterredirect">Retrieve a redirect</a> — <code>intercom.retrievehelpcenterredirect</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deletehelpcenterredirect">Delete a redirect</a> — <code>intercom.deletehelpcenterredirect</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listallcollections">List all collections</a> — <code>intercom.listallcollections</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createcollection">Create a collection</a> — <code>intercom.createcollection</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievecollection">Retrieve a collection</a> — <code>intercom.retrievecollection</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatecollection">Update a collection</a> — <code>intercom.updatecollection</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deletecollection">Delete a collection</a> — <code>intercom.deletecollection</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievehelpcenter">Retrieve a Help Center</a> — <code>intercom.retrievehelpcenter</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listhelpcenters">List all Help Centers</a> — <code>intercom.listhelpcenters</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listinternalarticles">List all articles</a> — <code>intercom.listinternalarticles</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createinternalarticle">Create an internal article</a> — <code>intercom.createinternalarticle</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrieveinternalarticle">Retrieve an internal article</a> — <code>intercom.retrieveinternalarticle</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updateinternalarticle">Update an internal article</a> — <code>intercom.updateinternalarticle</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deleteinternalarticle">Delete an internal article</a> — <code>intercom.deleteinternalarticle</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-attachtagtointernalarticle">Add a tag to an internal article</a> — <code>intercom.attachtagtointernalarticle</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-detachtagfrominternalarticle">Remove a tag from an internal article</a> — <code>intercom.detachtagfrominternalarticle</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-searchinternalarticles">Search for internal articles</a> — <code>intercom.searchinternalarticles</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listfolders">List all folders</a> — <code>intercom.listfolders</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createfolder">Create a folder</a> — <code>intercom.createfolder</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievefolder">Retrieve a folder</a> — <code>intercom.retrievefolder</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatefolder">Update a folder</a> — <code>intercom.updatefolder</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deletefolder">Delete a folder</a> — <code>intercom.deletefolder</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getipallowlist">Get IP allowlist settings</a> — <code>intercom.getipallowlist</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updateipallowlist">Update IP allowlist settings</a> — <code>intercom.updateipallowlist</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createorupdatecompany">Create or Update a company</a> — <code>intercom.createorupdatecompany</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievecompany">Retrieve companies</a> — <code>intercom.retrievecompany</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrieveacompanybyid">Retrieve a company by ID</a> — <code>intercom.retrieveacompanybyid</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatecompany">Update a company</a> — <code>intercom.updatecompany</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deletecompany">Delete a company</a> — <code>intercom.deletecompany</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listattachedcontacts">List attached contacts</a> — <code>intercom.listattachedcontacts</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listattachedsegmentsforcompanies">List attached segments for companies</a> — <code>intercom.listattachedsegmentsforcompanies</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listcompanynotes">List all company notes</a> — <code>intercom.listcompanynotes</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createcompanynote">Create a company note</a> — <code>intercom.createcompanynote</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-searchcompanies">Search companies</a> — <code>intercom.searchcompanies</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listallcompanies">List all companies</a> — <code>intercom.listallcompanies</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-scrolloverallcompanies">Scroll over all companies</a> — <code>intercom.scrolloverallcompanies</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-attachcontacttoacompany">Attach a Contact to a Company</a> — <code>intercom.attachcontacttoacompany</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listcompaniesforacontact">List attached companies for contact</a> — <code>intercom.listcompaniesforacontact</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-detachcontactfromacompany">Detach a contact from a company</a> — <code>intercom.detachcontactfromacompany</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listnotes">List all notes</a> — <code>intercom.listnotes</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createnote">Create a note</a> — <code>intercom.createnote</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listsegmentsforacontact">List attached segments for contact</a> — <code>intercom.listsegmentsforacontact</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listsubscriptionsforacontact">List subscriptions for a contact</a> — <code>intercom.listsubscriptionsforacontact</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-attachsubscriptiontypetocontact">Add subscription to a contact</a> — <code>intercom.attachsubscriptiontypetocontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-detachsubscriptiontypetocontact">Remove subscription from a contact</a> — <code>intercom.detachsubscriptiontypetocontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listtagsforacontact">List tags attached to a contact</a> — <code>intercom.listtagsforacontact</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-attachtagtocontact">Add tag to a contact</a> — <code>intercom.attachtagtocontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-detachtagfromcontact">Remove tag from a contact</a> — <code>intercom.detachtagfromcontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listdeletedcontacts">List deleted contacts</a> — <code>intercom.listdeletedcontacts</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatecontact">Update a contact</a> — <code>intercom.updatecontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-showcontact">Get a contact</a> — <code>intercom.showcontact</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deletecontact">Delete a contact</a> — <code>intercom.deletecontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-mergecontact">Merge a lead and a user</a> — <code>intercom.mergecontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-previewmergecontact">Preview a contact merge</a> — <code>intercom.previewmergecontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-searchcontacts">Search contacts</a> — <code>intercom.searchcontacts</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listcontactactivities">List all contact activities</a> — <code>intercom.listcontactactivities</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listcontacts">List all contacts</a> — <code>intercom.listcontacts</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createcontact">Create contact</a> — <code>intercom.createcontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-showcontactbyexternalid">Get a contact by External ID</a> — <code>intercom.showcontactbyexternalid</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-archivecontact">Archive contact</a> — <code>intercom.archivecontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-unarchivecontact">Unarchive contact</a> — <code>intercom.unarchivecontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listcontactbanners">List banners for a contact</a> — <code>intercom.listcontactbanners</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-dismisscontactbanner">Dismiss a banner for a contact</a> — <code>intercom.dismisscontactbanner</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-blockcontact">Block contact</a> — <code>intercom.blockcontact</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listcontactmergehistory">Get contact merge history</a> — <code>intercom.listcontactmergehistory</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-bulkcreatecontacts">Bulk create contacts</a> — <code>intercom.bulkcreatecontacts</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-bulkupdatecontacts">Bulk update contacts</a> — <code>intercom.bulkupdatecontacts</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-bulkdeletecontacts">Bulk delete contacts</a> — <code>intercom.bulkdeletecontacts</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-showbulkupdatecontactsjob">Get a bulk update job</a> — <code>intercom.showbulkupdatecontactsjob</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-bulkcontentactions">Run a bulk action on Knowledge Hub content</a> — <code>intercom.bulkcontentactions</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-searchcontent">Search knowledge base contents</a> — <code>intercom.searchcontent</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listcontentsnippets">List all content snippets</a> — <code>intercom.listcontentsnippets</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createcontentsnippet">Create a content snippet</a> — <code>intercom.createcontentsnippet</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getcontentsnippet">Retrieve a content snippet</a> — <code>intercom.getcontentsnippet</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatecontentsnippet">Update a content snippet</a> — <code>intercom.updatecontentsnippet</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deletecontentsnippet">Delete a content snippet</a> — <code>intercom.deletecontentsnippet</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-attachtagtocontentsnippet">Add a tag to a content snippet</a> — <code>intercom.attachtagtocontentsnippet</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-detachtagfromcontentsnippet">Remove a tag from a content snippet</a> — <code>intercom.detachtagfromcontentsnippet</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listdynamiccontents">List all dynamic content</a> — <code>intercom.listdynamiccontents</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createdynamiccontent">Create dynamic content</a> — <code>intercom.createdynamiccontent</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getdynamiccontent">Retrieve dynamic content</a> — <code>intercom.getdynamiccontent</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatedynamiccontent">Update dynamic content</a> — <code>intercom.updatedynamiccontent</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deletedynamiccontent">Delete dynamic content</a> — <code>intercom.deletedynamiccontent</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-attachtagtoconversation">Add tag to a conversation</a> — <code>intercom.attachtagtoconversation</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-detachtagfromconversation">Remove tag from a conversation</a> — <code>intercom.detachtagfromconversation</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listconversations">List all conversations</a> — <code>intercom.listconversations</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createconversation">Creates a conversation</a> — <code>intercom.createconversation</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrieveconversation">Retrieve a conversation</a> — <code>intercom.retrieveconversation</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updateconversation">Update a conversation</a> — <code>intercom.updateconversation</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deleteconversation">Delete a conversation</a> — <code>intercom.deleteconversation</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-searchconversations">Search conversations</a> — <code>intercom.searchconversations</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-replyconversation">Reply to a conversation</a> — <code>intercom.replyconversation</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-manageconversation">Manage a conversation</a> — <code>intercom.manageconversation</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-attachcontacttoconversation">Attach a contact to a conversation</a> — <code>intercom.attachcontacttoconversation</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-detachcontactfromconversation">Detach a contact from a group conversation</a> — <code>intercom.detachcontactfromconversation</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listhandlingevents">List handling events</a> — <code>intercom.listhandlingevents</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listhitlevents">List HITL events</a> — <code>intercom.listhitlevents</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listsideconversations">List side conversations</a> — <code>intercom.listsideconversations</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-redactconversation">Redact a conversation part</a> — <code>intercom.redactconversation</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-mergeconversation">Merge a conversation</a> — <code>intercom.mergeconversation</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-convertconversationtoticket">Convert a conversation to a ticket</a> — <code>intercom.convertconversationtoticket</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listdeletedconversationids">List all deleted conversation IDs</a> — <code>intercom.listdeletedconversationids</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listconversationattributes">List all conversation attributes</a> — <code>intercom.listconversationattributes</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createconversationattribute">Create a conversation attribute</a> — <code>intercom.createconversationattribute</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getconversationattribute">Get a conversation attribute</a> — <code>intercom.getconversationattribute</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updateconversationattribute">Update a conversation attribute</a> — <code>intercom.updateconversationattribute</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deleteconversationattribute">Delete (archive) a conversation attribute</a> — <code>intercom.deleteconversationattribute</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createconversationattributeoption">Add an option to a list conversation attribute</a> — <code>intercom.createconversationattributeoption</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updateconversationattributeoption">Update an option on a list conversation attribute</a> — <code>intercom.updateconversationattributeoption</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deleteconversationattributeoption">Archive an option on a list conversation attribute</a> — <code>intercom.deleteconversationattributeoption</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createcustomobjectinstances">Create or Update a Custom Object Instance</a> — <code>intercom.createcustomobjectinstances</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listcustomobjectinstances">List Custom Object Instances</a> — <code>intercom.listcustomobjectinstances</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getcustomobjectinstancesbyid">Get Custom Object Instance by ID</a> — <code>intercom.getcustomobjectinstancesbyid</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deletecustomobjectinstancesbyid">Delete a Custom Object Instance by ID</a> — <code>intercom.deletecustomobjectinstancesbyid</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-lisdataattributes">List all data attributes</a> — <code>intercom.lisdataattributes</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createdataattribute">Create a data attribute</a> — <code>intercom.createdataattribute</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatedataattribute">Update a data attribute</a> — <code>intercom.updatedataattribute</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listdataconnectors">List all data connectors</a> — <code>intercom.listdataconnectors</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createdataconnector">Create a data connector</a> — <code>intercom.createdataconnector</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievedataconnector">Retrieve a data connector</a> — <code>intercom.retrievedataconnector</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deletedataconnector">Delete a data connector</a> — <code>intercom.deletedataconnector</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatedataconnector">Update a data connector</a> — <code>intercom.updatedataconnector</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listdataconnectorexecutionresults">List execution results for a data connector</a> — <code>intercom.listdataconnectorexecutionresults</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-showdataconnectorexecutionresult">Retrieve an execution result</a> — <code>intercom.showdataconnectorexecutionresult</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listdataconnectorversions">List versions of a data connector</a> — <code>intercom.listdataconnectorversions</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievedataconnectorversion">Retrieve a version of a data connector</a> — <code>intercom.retrievedataconnectorversion</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatedataconnectorversion">Update the note on a data connector version</a> — <code>intercom.updatedataconnectorversion</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createdataevent">Submit a data event</a> — <code>intercom.createdataevent</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-lisdataevents">List all data events</a> — <code>intercom.lisdataevents</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-dataeventsummaries">Create event summaries</a> — <code>intercom.dataeventsummaries</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createdataexport">Create content data export</a> — <code>intercom.createdataexport</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getdataexport">Show content data export</a> — <code>intercom.getdataexport</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-canceldataexport">Cancel content data export</a> — <code>intercom.canceldataexport</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-downloaddataexport">Download content data export</a> — <code>intercom.downloaddataexport</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-jobsstatus">Retrieve job status</a> — <code>intercom.jobsstatus</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createmessage">Create a message</a> — <code>intercom.createmessage</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievewhatsappmessagestatus">Retrieve WhatsApp message delivery status</a> — <code>intercom.retrievewhatsappmessagestatus</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getwhatsappmessagestatus">Get statuses of all messages sent based on the specified ruleset_id</a> — <code>intercom.getwhatsappmessagestatus</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listnewsitems">List all news items</a> — <code>intercom.listnewsitems</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createnewsitem">Create a news item</a> — <code>intercom.createnewsitem</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievenewsitem">Retrieve a news item</a> — <code>intercom.retrievenewsitem</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatenewsitem">Update a news item</a> — <code>intercom.updatenewsitem</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deletenewsitem">Delete a news item</a> — <code>intercom.deletenewsitem</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listlivenewsfeeditems">List all live newsfeed items</a> — <code>intercom.listlivenewsfeeditems</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listnewsfeeds">List all newsfeeds</a> — <code>intercom.listnewsfeeds</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievenewsfeed">Retrieve a newsfeed</a> — <code>intercom.retrievenewsfeed</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievenote">Retrieve a note</a> — <code>intercom.retrievenote</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deletenote">Delete a note</a> — <code>intercom.deletenote</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listsegments">List all segments</a> — <code>intercom.listsegments</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievesegment">Retrieve a segment</a> — <code>intercom.retrievesegment</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listsubscriptiontypes">List subscription types</a> — <code>intercom.listsubscriptiontypes</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getsubscriptiontype">Retrieve a subscription type</a> — <code>intercom.getsubscriptiontype</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createphoneswitch">Create a phone Switch</a> — <code>intercom.createphoneswitch</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listcalls">List all calls</a> — <code>intercom.listcalls</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-showcall">Get a call</a> — <code>intercom.showcall</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-showcalltranscript">Get call transcript by call id</a> — <code>intercom.showcalltranscript</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listcallswithtranscripts">List calls with transcripts</a> — <code>intercom.listcallswithtranscripts</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listtags">List all tags</a> — <code>intercom.listtags</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createtag">Create or update a tag, Tag or untag companies, Tag contacts</a> — <code>intercom.createtag</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-findtag">Find a specific tag</a> — <code>intercom.findtag</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deletetag">Delete tag</a> — <code>intercom.deletetag</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listteams">List all teams</a> — <code>intercom.listteams</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrieveteam">Retrieve a team</a> — <code>intercom.retrieveteam</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getteammetrics">Retrieve team metrics</a> — <code>intercom.getteammetrics</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listticketstates">List all ticket states</a> — <code>intercom.listticketstates</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createtickettypeattribute">Create a new attribute for a ticket type</a> — <code>intercom.createtickettypeattribute</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatetickettypeattribute">Update an existing attribute for a ticket type</a> — <code>intercom.updatetickettypeattribute</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listtickettypes">List all ticket types</a> — <code>intercom.listtickettypes</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createtickettype">Create a ticket type</a> — <code>intercom.createtickettype</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-gettickettype">Retrieve a ticket type</a> — <code>intercom.gettickettype</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatetickettype">Update a ticket type</a> — <code>intercom.updatetickettype</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-replyticket">Reply to a ticket</a> — <code>intercom.replyticket</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-attachtagtoticket">Add tag to a ticket</a> — <code>intercom.attachtagtoticket</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-detachtagfromticket">Remove tag from a ticket</a> — <code>intercom.detachtagfromticket</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-linkconversationtoticket">Link a conversation to a ticket</a> — <code>intercom.linkconversationtoticket</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-unlinkconversationfromticket">Unlink a conversation from a ticket</a> — <code>intercom.unlinkconversationfromticket</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-createticket">Create a ticket</a> — <code>intercom.createticket</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-enqueuecreateticket">Enqueue create ticket</a> — <code>intercom.enqueuecreateticket</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updateticket">Update a ticket</a> — <code>intercom.updateticket</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-getticket">Retrieve a ticket</a> — <code>intercom.getticket</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-deleteticket">Delete a ticket</a> — <code>intercom.deleteticket</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-changetickettype">Change ticket type</a> — <code>intercom.changetickettype</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-searchtickets">Search tickets</a> — <code>intercom.searchtickets</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-updatevisitor">Update a visitor</a> — <code>intercom.updatevisitor</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievevisitorwithuserid">Retrieve a visitor with User ID</a> — <code>intercom.retrievevisitorwithuserid</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-convertvisitor">Convert a visitor</a> — <code>intercom.convertvisitor</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listbrands">List all brands</a> — <code>intercom.listbrands</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrievebrand">Retrieve a brand</a> — <code>intercom.retrievebrand</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-listemails">List all email settings</a> — <code>intercom.listemails</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-retrieveemail">Retrieve an email setting</a> — <code>intercom.retrieveemail</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-registerfinvoicecall">Register a Fin Voice call</a> — <code>intercom.registerfinvoicecall</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-collectfinvoicecallbyid">Collect Fin Voice call by ID</a> — <code>intercom.collectfinvoicecallbyid</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-collectfinvoicecallbyexternalid">Collect Fin Voice call by external ID</a> — <code>intercom.collectfinvoicecallbyexternalid</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-collectfinvoicecallbyphonenumber">Collect Fin Voice call by phone number</a> — <code>intercom.collectfinvoicecallbyphonenumber</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-collectfinvoicecallsbyconversationid">Collect Fin Voice calls by conversation ID</a> — <code>intercom.collectfinvoicecallsbyconversationid</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/intercom#command-intercom-exportworkflow">Export a workflow</a> — <code>intercom.exportworkflow</code></td>
<td>Read</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/intercom">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Intercom, then enter the issued values in the connection form below.</p>
<ol>
<li>In the Intercom Developer Hub, open or create an app for the intended workspace, configure the required permissions and obtain its access token following the official authentication guide. Paste it into this connection’s Intercom workspace app access token field. Start with identifyadmin; selected commands must match the token’s permissions. This pinned contract uses Intercom-Version 2.17 and the default api.intercom.io region; EU/AU regional origins require separate reviewed configuration. Conversations, contacts and outbound content can affect customers. Save only needed commands and create a separate scoped Tooluse.net API key. Never expose the Intercom token in the MCP URL.</li>
</ol>
<p><a href="https://developers.intercom.com/docs/build-an-integration/learn-more/authentication">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>Intercom workspace app access token</td>
<td>Required</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {}
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-intercom-identifyadmin">
<summary><span>Identify an admin — <code>intercom.<wbr>identifyadmin</code></span></summary>
<p>Run <strong>Identify an admin</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.identifyadmin">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.identifyadmin">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getmacro">
<summary><span>Retrieve a macro — <code>intercom.<wbr>getmacro</code></span></summary>
<p>Run <strong>Retrieve a macro</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getmacro">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the macro</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getmacro">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listmacros">
<summary><span>List all macros — <code>intercom.<wbr>listmacros</code></span></summary>
<p>Run <strong>List all macros</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listmacros">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results per page</td>
<td><code>default: 50; minimum: 1; maximum: 150</code></td>
</tr>
<tr>
<td><code>query.starting_after</code></td>
<td>string</td>
<td>Optional</td>
<td>Base64-encoded cursor containing [updated_at, id] for pagination</td>
<td></td>
</tr>
<tr>
<td><code>query.updated_since</code></td>
<td>integer</td>
<td>Optional</td>
<td>Unix timestamp to filter macros updated after this time</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listmacros">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-setawayadmin">
<summary><span>Set an admin to away — <code>intercom.<wbr>setawayadmin</code></span></summary>
<p>Run <strong>Set an admin to away</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.setawayadmin">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.admin_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier of a given admin</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.away_mode_enabled</code></td>
<td>boolean</td>
<td>Required</td>
<td>Set to <code>true</code> to change the status of the admin to away, or <code>false</code> to set them back to active.</td>
<td></td>
</tr>
<tr>
<td><code>body.away_mode_reassign</code></td>
<td>boolean</td>
<td>Required</td>
<td>Set to &quot;true&quot; to assign any new conversation replies to your default inbox.</td>
<td></td>
</tr>
<tr>
<td><code>body.away_status_reason_id</code></td>
<td>integer</td>
<td>Optional</td>
<td>The unique identifier of the away status reason. Only allowed when <code>away_mode_enabled</code> is <code>true</code>, and the reason can&#39;t be archived, unless it is already the admin&#39;s current reason. Required if your workspace makes away status reasons mandatory.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.setawayadmin">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "admin_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listactivitylogs">
<summary><span>List all activity logs — <code>intercom.<wbr>listactivitylogs</code></span></summary>
<p>Run <strong>List all activity logs</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listactivitylogs">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.created_at_after</code></td>
<td>string</td>
<td>Optional</td>
<td>The start date that you request data for. It must be formatted as a UNIX timestamp. If you leave it out, it defaults to 30 days before the request.</td>
<td></td>
</tr>
<tr>
<td><code>query.created_at_before</code></td>
<td>string</td>
<td>Optional</td>
<td>The end date that you request data for. It must be formatted as a UNIX timestamp. If you leave it out, it defaults to the time of the request.</td>
<td></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page number of results to return. Defaults to the first page.</td>
<td><code>default: 1</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results per page. Must be between 1 and 250.</td>
<td><code>default: 20; minimum: 1; maximum: 250</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listactivitylogs">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-searchactivitylogs">
<summary><span>Search activity logs — <code>intercom.<wbr>searchactivitylogs</code></span></summary>
<p>Run <strong>Search activity logs</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.searchactivitylogs">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.created_at_after</code></td>
<td>integer</td>
<td>Optional</td>
<td>The start date that you request data for. It must be formatted as a UNIX timestamp. If you leave it out, it defaults to 30 days before the request.</td>
<td><code>format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>body.created_at_before</code></td>
<td>integer</td>
<td>Optional</td>
<td>The end date that you request data for. It must be formatted as a UNIX timestamp. If you leave it out, it defaults to the time of the request.</td>
<td><code>format: &quot;date-time&quot;</code></td>
</tr>
<tr>
<td><code>body.event_types</code></td>
<td>array</td>
<td>Optional</td>
<td>An optional list of event types to filter activity logs by. Use the list all activity log event types endpoint to retrieve available values.</td>
<td></td>
</tr>
<tr>
<td><code>body.event_types[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page number of results to return.</td>
<td><code>default: 1</code></td>
</tr>
<tr>
<td><code>body.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results per page. Must be between 1 and 250.</td>
<td><code>default: 20; minimum: 1; maximum: 250</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.searchactivitylogs">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "created_at_after": 1677253093,
    "created_at_before": 1677861493,
    "event_types": [
      "app_name_change",
      "message_state_change"
    ]
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listactivitylogeventtypes">
<summary><span>List all activity log event types — <code>intercom.<wbr>listactivitylogevent<wbr>types</code></span></summary>
<p>Run <strong>List all activity log event types</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listactivitylogeventtypes">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listactivitylogeventtypes">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listadmins">
<summary><span>List all admins — <code>intercom.<wbr>listadmins</code></span></summary>
<p>Run <strong>List all admins</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listadmins">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.display_avatar</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If set to true, the response will include the admin&#39;s avatar object containing the image URL. Defaults to false.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listadmins">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getofficehoursexception">
<summary><span>Retrieve an office hours exception — <code>intercom.<wbr>getofficehoursexcept<wbr>ion</code></span></summary>
<p>Run <strong>Retrieve an office hours exception</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getofficehoursexception">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.office_hours_schedule_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the office hours schedule.</td>
<td></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the office hours exception.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getofficehoursexception">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "office_hours_schedule_id": "123",
    "id": "456"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updateofficehoursexception">
<summary><span>Update an office hours exception — <code>intercom.<wbr>updateofficehoursexc<wbr>eption</code></span></summary>
<p>Run <strong>Update an office hours exception</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updateofficehoursexception">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.office_hours_schedule_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the office hours schedule.</td>
<td></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the office hours exception.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_office_hours_exception_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updateofficehoursexception">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "office_hours_schedule_id": "123",
    "id": "456"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deleteofficehoursexception">
<summary><span>Delete an office hours exception — <code>intercom.<wbr>deleteofficehoursexc<wbr>eption</code></span></summary>
<p>Run <strong>Delete an office hours exception</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deleteofficehoursexception">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.office_hours_schedule_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the office hours schedule.</td>
<td></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the office hours exception.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deleteofficehoursexception">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "office_hours_schedule_id": "123",
    "id": "456"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listofficehoursexceptions">
<summary><span>List all office hours exceptions — <code>intercom.<wbr>listofficehoursexcep<wbr>tions</code></span></summary>
<p>Run <strong>List all office hours exceptions</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listofficehoursexceptions">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.office_hours_schedule_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the office hours schedule.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listofficehoursexceptions">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "office_hours_schedule_id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createofficehoursexception">
<summary><span>Create an office hours exception — <code>intercom.<wbr>createofficehoursexc<wbr>eption</code></span></summary>
<p>Run <strong>Create an office hours exception</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createofficehoursexception">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.office_hours_schedule_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the office hours schedule.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_office_hours_exception_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createofficehoursexception">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "office_hours_schedule_id": "123"
  },
  "body": {
    "exception_date": "2026-12-25",
    "exception_type": "closed"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getofficehoursschedule">
<summary><span>Retrieve an office hours schedule — <code>intercom.<wbr>getofficehoursschedu<wbr>le</code></span></summary>
<p>Run <strong>Retrieve an office hours schedule</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getofficehoursschedule">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the office hours schedule.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getofficehoursschedule">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updateofficehoursschedule">
<summary><span>Update an office hours schedule — <code>intercom.<wbr>updateofficehourssch<wbr>edule</code></span></summary>
<p>Run <strong>Update an office hours schedule</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updateofficehoursschedule">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the office hours schedule.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_office_hours_schedule_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updateofficehoursschedule">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deleteofficehoursschedule">
<summary><span>Delete an office hours schedule — <code>intercom.<wbr>deleteofficehourssch<wbr>edule</code></span></summary>
<p>Run <strong>Delete an office hours schedule</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deleteofficehoursschedule">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the office hours schedule.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deleteofficehoursschedule">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listofficehoursschedules">
<summary><span>List all office hours schedules — <code>intercom.<wbr>listofficehourssched<wbr>ules</code></span></summary>
<p>Run <strong>List all office hours schedules</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listofficehoursschedules">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listofficehoursschedules">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createofficehoursschedule">
<summary><span>Create an office hours schedule — <code>intercom.<wbr>createofficehourssch<wbr>edule</code></span></summary>
<p>Run <strong>Create an office hours schedule</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createofficehoursschedule">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_office_hours_schedule_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createofficehoursschedule">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "name": "Standard Support Hours",
    "time_intervals": []
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrieveadmin">
<summary><span>Retrieve an admin — <code>intercom.<wbr>retrieveadmin</code></span></summary>
<p>Run <strong>Retrieve an admin</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrieveadmin">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.admin_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier of a given admin</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrieveadmin">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "admin_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-removeadmin">
<summary><span>Remove an admin — <code>intercom.<wbr>removeadmin</code></span></summary>
<p>Run <strong>Remove an admin</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.removeadmin">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.admin_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier of the admin to remove.</td>
<td></td>
</tr>
<tr>
<td><code>query.reassign_messages_admin_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier of a human admin to reassign the removed admin&#39;s auto-message ownership to.</td>
<td></td>
</tr>
<tr>
<td><code>query.reassign_owner_admin_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier of a human admin to reassign the removed admin&#39;s ownership (of users and leads) to.</td>
<td></td>
</tr>
<tr>
<td><code>query.reassign_articles_author_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier of a human admin to reassign the removed admin&#39;s article authorship to.</td>
<td></td>
</tr>
<tr>
<td><code>query.reassign_conversations_admin_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The ID of an admin with Inbox access, or a team, to reassign the removed admin&#39;s conversation replies to. Pass <code>0</code> to leave conversations unassigned.</td>
<td></td>
</tr>
<tr>
<td><code>query.reassign_replies_teams</code></td>
<td>array</td>
<td>Optional</td>
<td>A list of teams and the admin each team&#39;s conversation replies should be reassigned to.</td>
<td></td>
</tr>
<tr>
<td><code>query.reassign_replies_teams[]</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.reassign_replies_teams[].team_id</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.reassign_replies_teams[].assignee_id</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.removeadmin">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "admin_id": 123,
    "reassign_messages_admin_id": 456,
    "reassign_owner_admin_id": 456,
    "reassign_articles_author_id": 456,
    "reassign_conversations_admin_id": 456
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listcontentimportsources">
<summary><span>List content import sources — <code>intercom.<wbr>listcontentimportsou<wbr>rces</code></span></summary>
<p>Run <strong>List content import sources</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listcontentimportsources">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to the first page.</td>
<td><code>default: 1; minimum: 1</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page. Maximum 150.</td>
<td><code>default: 50; minimum: 1; maximum: 150</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listcontentimportsources">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createcontentimportsource">
<summary><span>Create a content import source — <code>intercom.<wbr>createcontentimports<wbr>ource</code></span></summary>
<p>Run <strong>Create a content import source</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createcontentimportsource">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_content_import_source_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createcontentimportsource">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deletecontentimportsource">
<summary><span>Delete a content import source — <code>intercom.<wbr>deletecontentimports<wbr>ource</code></span></summary>
<p>Run <strong>Delete a content import source</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deletecontentimportsource">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.source_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the content import source which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deletecontentimportsource">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "source_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getcontentimportsource">
<summary><span>Retrieve a content import source — <code>intercom.<wbr>getcontentimportsour<wbr>ce</code></span></summary>
<p>Run <strong>Retrieve a content import source</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getcontentimportsource">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.source_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the content import source which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getcontentimportsource">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "source_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatecontentimportsource">
<summary><span>Update a content import source — <code>intercom.<wbr>updatecontentimports<wbr>ource</code></span></summary>
<p>Run <strong>Update a content import source</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatecontentimportsource">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.source_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the content import source which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_content_import_source_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatecontentimportsource">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "source_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listexternalpages">
<summary><span>List external pages — <code>intercom.<wbr>listexternalpages</code></span></summary>
<p>Run <strong>List external pages</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listexternalpages">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to the first page. <code>page</code> cannot exceed 5,001, and <code>page</code> multiplied by <code>per_page</code> cannot exceed 10,000. Past 5,001 the API returns a 400 <code>parameter_invalid</code> error; past 10,000 results it returns a 400 <code>bad_request</code> error with the message <code>page limit reached, please use scroll API</code>.</td>
<td><code>default: 1; minimum: 1</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page. Maximum 150.</td>
<td><code>default: 50; minimum: 1; maximum: 150</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listexternalpages">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createexternalpage">
<summary><span>Create an external page (or update an external page by external ID) — <code>intercom.<wbr>createexternalpage</code></span></summary>
<p>Run <strong>Create an external page (or update an external page by external ID)</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createexternalpage">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_external_page_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createexternalpage">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deleteexternalpage">
<summary><span>Delete an external page — <code>intercom.<wbr>deleteexternalpage</code></span></summary>
<p>Run <strong>Delete an external page</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deleteexternalpage">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.page_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the external page which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deleteexternalpage">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "page_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getexternalpage">
<summary><span>Retrieve an external page — <code>intercom.<wbr>getexternalpage</code></span></summary>
<p>Run <strong>Retrieve an external page</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getexternalpage">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.page_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the external page which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getexternalpage">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "page_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updateexternalpage">
<summary><span>Update an external page — <code>intercom.<wbr>updateexternalpage</code></span></summary>
<p>Run <strong>Update an external page</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updateexternalpage">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.page_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the external page which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_external_page_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updateexternalpage">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "page_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-attachtagtoexternalpage">
<summary><span>Add a tag to an external page — <code>intercom.<wbr>attachtagtoexternalp<wbr>age</code></span></summary>
<p>Run <strong>Add a tag to an external page</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.attachtagtoexternalpage">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.external_page_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the external page which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the tag to apply, as given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body.admin_id</code></td>
<td>string &#124; null</td>
<td>Optional</td>
<td>Optional id of the teammate to attribute the tagging to. Defaults to the authenticating teammate.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.attachtagtoexternalpage">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "external_page_id": "1234"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-detachtagfromexternalpage">
<summary><span>Remove a tag from an external page — <code>intercom.<wbr>detachtagfromexterna<wbr>lpage</code></span></summary>
<p>Run <strong>Remove a tag from an external page</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.detachtagfromexternalpage">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.external_page_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the external page which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the tag to remove, as given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.detachtagfromexternalpage">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "external_page_id": "1234",
    "id": "7522907"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listarticles">
<summary><span>List all articles — <code>intercom.<wbr>listarticles</code></span></summary>
<p>Run <strong>List all articles</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listarticles">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to the first page.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page. Defaults to 25. Maximum is 250.</td>
<td><code>maximum: 250</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listarticles">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createarticle">
<summary><span>Create an article — <code>intercom.<wbr>createarticle</code></span></summary>
<p>Run <strong>Create an article</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createarticle">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_article_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createarticle">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievearticle">
<summary><span>Retrieve an article — <code>intercom.<wbr>retrievearticle</code></span></summary>
<p>Run <strong>Retrieve an article</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievearticle">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.article_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the article which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievearticle">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "article_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatearticle">
<summary><span>Update an article — <code>intercom.<wbr>updatearticle</code></span></summary>
<p>Run <strong>Update an article</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatearticle">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.article_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the article which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_article_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatearticle">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "article_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deletearticle">
<summary><span>Delete an article — <code>intercom.<wbr>deletearticle</code></span></summary>
<p>Run <strong>Delete an article</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deletearticle">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.article_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the article which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deletearticle">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "article_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievearticledraft">
<summary><span>Retrieve an article draft — <code>intercom.<wbr>retrievearticledraft</code></span></summary>
<p>Run <strong>Retrieve an article draft</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievearticledraft">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the article which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievearticledraft">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-stagearticledraft">
<summary><span>Stage an article draft — <code>intercom.<wbr>stagearticledraft</code></span></summary>
<p>Run <strong>Stage an article draft</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.stagearticledraft">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the article which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_article_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.stagearticledraft">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-publisharticledraft">
<summary><span>Publish an article draft — <code>intercom.<wbr>publisharticledraft</code></span></summary>
<p>Run <strong>Publish an article draft</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.publisharticledraft">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the article which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/publish_article_draft_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.publisharticledraft">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-attachtagtoarticle">
<summary><span>Add a tag to an article — <code>intercom.<wbr>attachtagtoarticle</code></span></summary>
<p>Run <strong>Add a tag to an article</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.attachtagtoarticle">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.article_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the article which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the tag to apply, as given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body.admin_id</code></td>
<td>string &#124; null</td>
<td>Optional</td>
<td>Optional id of the teammate to attribute the tagging to. Defaults to the authenticating teammate. Does not affect authorization.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.attachtagtoarticle">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "article_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-detachtagfromarticle">
<summary><span>Remove a tag from an article — <code>intercom.<wbr>detachtagfromarticle</code></span></summary>
<p>Run <strong>Remove a tag from an article</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.detachtagfromarticle">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.article_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the article which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the tag to remove, as given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.detachtagfromarticle">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "article_id": 123,
    "id": "7522907"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listarticleversions">
<summary><span>List article versions — <code>intercom.<wbr>listarticleversions</code></span></summary>
<p>Run <strong>List article versions</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listarticleversions">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.article_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the article whose versions you are listing.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to the first page.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page. Defaults to 10.</td>
<td></td>
</tr>
<tr>
<td><code>query.locale</code></td>
<td>string</td>
<td>Optional</td>
<td>Filter versions to a specific locale. Use the locale identifier (for example <code>en</code>, <code>fr</code>). If the article has no content in that locale, a <code>400</code> is returned.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listarticleversions">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "article_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievearticleversion">
<summary><span>Retrieve an article version — <code>intercom.<wbr>retrievearticleversi<wbr>on</code></span></summary>
<p>Run <strong>Retrieve an article version</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievearticleversion">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.article_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the article.</td>
<td></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the version.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.locale</code></td>
<td>string</td>
<td>Optional</td>
<td>Return the version&#39;s content for a specific locale. If the article has no content in that locale, a <code>400</code> is returned.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievearticleversion">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "article_id": 123,
    "id": "301"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-searcharticles">
<summary><span>Search for articles — <code>intercom.<wbr>searcharticles</code></span></summary>
<p>Run <strong>Search for articles</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.searcharticles">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.phrase</code></td>
<td>string</td>
<td>Optional</td>
<td>The phrase within your articles to search for. Maximum length is 500 characters.</td>
<td><code>maxLength: 500</code></td>
</tr>
<tr>
<td><code>query.state</code></td>
<td>string</td>
<td>Optional</td>
<td>The state of the Articles returned. One of <code>published</code>, <code>draft</code> or <code>all</code>. Defaults to <code>published</code>.</td>
<td><code>enum: [&quot;published&quot;,&quot;draft&quot;,&quot;all&quot;]; default: &quot;published&quot;</code></td>
</tr>
<tr>
<td><code>query.help_center_id</code></td>
<td>integer</td>
<td>Optional</td>
<td>The ID of the Help Center to search in.</td>
<td></td>
</tr>
<tr>
<td><code>query.highlight</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Return a highlighted version of the matching content within your articles. Refer to the response schema for more details.</td>
<td></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to the first page.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page. Defaults to 10.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.searcharticles">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listawaystatusreasons">
<summary><span>List all away status reasons — <code>intercom.<wbr>listawaystatusreason<wbr>s</code></span></summary>
<p>Run <strong>List all away status reasons</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listawaystatusreasons">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listawaystatusreasons">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listaudiences">
<summary><span>List all audiences — <code>intercom.<wbr>listaudiences</code></span></summary>
<p>Run <strong>List all audiences</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listaudiences">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to the first page. Values below 1 are treated as 1.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page. Defaults to 50. Values above 50 are reduced to 50, and values below 1 are treated as 1.</td>
<td><code>maximum: 50</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listaudiences">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createaudience">
<summary><span>Create an audience — <code>intercom.<wbr>createaudience</code></span></summary>
<p>Run <strong>Create an audience</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createaudience">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_audience_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createaudience">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "name": "VIP Customers"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrieveaudience">
<summary><span>Retrieve an audience — <code>intercom.<wbr>retrieveaudience</code></span></summary>
<p>Run <strong>Retrieve an audience</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrieveaudience">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the audience.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrieveaudience">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updateaudience">
<summary><span>Update an audience — <code>intercom.<wbr>updateaudience</code></span></summary>
<p>Run <strong>Update an audience</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updateaudience">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the audience.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_audience_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updateaudience">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deleteaudience">
<summary><span>Delete an audience — <code>intercom.<wbr>deleteaudience</code></span></summary>
<p>Run <strong>Delete an audience</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deleteaudience">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the audience.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deleteaudience">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-post--export-reporting_data-enqueue">
<summary><span>Enqueue a new reporting data export job — <code>intercom.<wbr>post-<wbr>.<wbr>export.<wbr>reporting_<wbr>data.<wbr>enqueue</code></span></summary>
<p>Run <strong>Enqueue a new reporting data export job</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.post-.export.reporting_data.enqueue">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.dataset_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.attribute_ids</code></td>
<td>array</td>
<td>Required</td>
<td>List of attribute identifiers to include in the export. Requires qualified_id format (e.g., &quot;people.Brand&quot;, &quot;standard.conversation_id&quot;). Use the qualified_id returned from the get_datasets response.</td>
<td></td>
</tr>
<tr>
<td><code>body.attribute_ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.start_time</code></td>
<td>integer</td>
<td>Required</td>
<td>Start of the export period, as a Unix timestamp in seconds. Must be within your workspace&#39;s reporting data retention period, which is 2 years by default (3 years for workspaces with extended retention).</td>
<td></td>
</tr>
<tr>
<td><code>body.end_time</code></td>
<td>integer</td>
<td>Required</td>
<td>End of the export period, as a Unix timestamp in seconds. Must not be earlier than start_time and must also be within the retention period.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.post-.export.reporting_data.enqueue">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "dataset_id": "conversation",
    "attribute_ids": [
      "standard.conversation_id",
      "timestamp.conversation_started_at"
    ],
    "start_time": 1788220800,
    "end_time": 1788307200
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-get--export-reporting_data--job_identifier-">
<summary><span>Get export job status — <code>intercom.<wbr>get-<wbr>.<wbr>export.<wbr>reporting_<wbr>data.<wbr>-<wbr>job_<wbr>identifier-<wbr></code></span></summary>
<p>Run <strong>Get export job status</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.get-.export.reporting_data.-job_identifier-">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.job_identifier</code></td>
<td>string</td>
<td>Required</td>
<td>Unique identifier of the job.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.get-.export.reporting_data.-job_identifier-">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "job_identifier": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-get--export-reporting_data-get_datasets">
<summary><span>List available datasets and attributes — <code>intercom.<wbr>get-<wbr>.<wbr>export.<wbr>reporting_<wbr>data.<wbr>get_<wbr>datasets</code></span></summary>
<p>Run <strong>List available datasets and attributes</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.get-.export.reporting_data.get_datasets">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.get-.export.reporting_data.get_datasets">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-startfinconversation">
<summary><span>Start a conversation with Fin — <code>intercom.<wbr>startfinconversation</code></span></summary>
<p>Run <strong>Start a conversation with Fin</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.startfinconversation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.conversation_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the conversation that is calling Fin via this API.</td>
<td></td>
</tr>
<tr>
<td><code>body.message</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/fin_agent_message&quot;</code></td>
</tr>
<tr>
<td><code>body.user</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/fin_agent_user&quot;</code></td>
</tr>
<tr>
<td><code>body.attachments</code></td>
<td>array</td>
<td>Optional</td>
<td>An array of attachments to include with the message. Maximum of 10 attachments.</td>
<td><code>maxItems: 10</code></td>
</tr>
<tr>
<td><code>body.attachments[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/fin_agent_attachment&quot;</code></td>
</tr>
<tr>
<td><code>body.conversation_metadata</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/fin_agent_conversation_metadata&quot;</code></td>
</tr>
<tr>
<td><code>body.environment</code></td>
<td>string</td>
<td>Optional</td>
<td>The identifier of the environment to start the conversation in. Only Fin for Platforms workspaces use it; other workspaces ignore it. Use the same value as <code>messenger_environment</code> in your Messenger installation. Defaults to the workspace&#39;s default environment. On a Fin for Platforms workspace, an identifier that matches no environment returns a 422 error.</td>
<td></td>
</tr>
<tr>
<td><code>body.response_format</code></td>
<td>string</td>
<td>Optional</td>
<td>The format of the <code>body</code> in Fin&#39;s replies. Defaults to <code>html</code>. Requesting <code>markdown</code> on a workspace where it is not enabled returns a 403 error.</td>
<td><code>enum: [&quot;html&quot;,&quot;markdown&quot;]; default: &quot;html&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.startfinconversation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "conversation_id": "ext-123",
    "message": {
      "author": "user",
      "body": "How can I see my account details?",
      "timestamp": "2025-01-24T10:01:20.000Z"
    },
    "user": {
      "id": "123456",
      "name": "John Doe",
      "email": "john.doe@example.com"
    }
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-replytofin">
<summary><span>Reply to Fin — <code>intercom.<wbr>replytofin</code></span></summary>
<p>Run <strong>Reply to Fin</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.replytofin">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.conversation_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the conversation.</td>
<td></td>
</tr>
<tr>
<td><code>body.message</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/fin_agent_message&quot;</code></td>
</tr>
<tr>
<td><code>body.user</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/fin_agent_user&quot;</code></td>
</tr>
<tr>
<td><code>body.attachments</code></td>
<td>array</td>
<td>Optional</td>
<td>An array of attachments to include with the message. Maximum of 10 attachments.</td>
<td><code>maxItems: 10</code></td>
</tr>
<tr>
<td><code>body.attachments[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/fin_agent_attachment&quot;</code></td>
</tr>
<tr>
<td><code>body.response_format</code></td>
<td>string</td>
<td>Optional</td>
<td>The format of the <code>body</code> in Fin&#39;s replies. Defaults to <code>html</code>. Requesting <code>markdown</code> on a workspace where it is not enabled returns a 403 error.</td>
<td><code>enum: [&quot;html&quot;,&quot;markdown&quot;]; default: &quot;html&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.replytofin">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "conversation_id": "123456",
    "message": {
      "author": "user",
      "body": "Here's the information you requested.",
      "timestamp": "2025-01-24T09:01:00.000Z"
    },
    "user": {
      "id": "123456",
      "name": "John Doe",
      "email": "john.doe@example.com"
    }
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-submitfincsat">
<summary><span>Submit a CSAT rating — <code>intercom.<wbr>submitfincsat</code></span></summary>
<p>Run <strong>Submit a CSAT rating</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.submitfincsat">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.conversation_id</code></td>
<td>string</td>
<td>Required</td>
<td>Your external conversation ID — the same ID you started the conversation with, and the one echoed on the <code>csat_requested</code> event.</td>
<td></td>
</tr>
<tr>
<td><code>body.rating</code></td>
<td>string</td>
<td>Required</td>
<td>The rating the user selected — one of the <code>key</code> values from the <code>csat_requested</code> event&#39;s options.</td>
<td><code>enum: [&quot;terrible&quot;,&quot;bad&quot;,&quot;ok&quot;,&quot;good&quot;,&quot;amazing&quot;]</code></td>
</tr>
<tr>
<td><code>body.remark</code></td>
<td>string</td>
<td>Optional</td>
<td>Optional free-text comment the user left alongside the rating. Can be added to an already-rated survey, but only once — the rating locks after a remark is recorded.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.submitfincsat">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "conversation_id": "ext-123",
    "rating": "amazing"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listfincapabilities">
<summary><span>Discover Fin's capabilities — <code>intercom.<wbr>listfincapabilities</code></span></summary>
<p>Run <strong>Discover Fin&#39;s capabilities</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listfincapabilities">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.user</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.user</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/fin_agent_user&quot;</code></td>
</tr>
<tr>
<td><code>body.user</code></td>
<td>—</td>
<td>Required</td>
<td>The user to list capabilities for. If no user exists for the id, one is created from the supplied details; if the user already exists, the supplied email and attributes update it.</td>
<td><code>allOf[2]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listfincapabilities">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "user": {
      "id": "123456"
    }
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-askfin">
<summary><span>Ask Fin — <code>intercom.<wbr>askfin</code></span></summary>
<p>Run <strong>Ask Fin</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.askfin">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.conversation_id</code></td>
<td>string</td>
<td>Required</td>
<td>Your external conversation ID. Fin creates a conversation for this ID. If a conversation already exists for it, use <code>/fin/reply</code> instead.</td>
<td></td>
</tr>
<tr>
<td><code>body.message</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/fin_agent_message&quot;</code></td>
</tr>
<tr>
<td><code>body.user</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/fin_agent_user&quot;</code></td>
</tr>
<tr>
<td><code>body.conversation_metadata</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/fin_agent_conversation_metadata&quot;</code></td>
</tr>
<tr>
<td><code>body.attachments</code></td>
<td>array</td>
<td>Optional</td>
<td>An array of attachments to include with the message. Maximum of 10 attachments.</td>
<td><code>maxItems: 10</code></td>
</tr>
<tr>
<td><code>body.attachments[]</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/fin_agent_attachment&quot;</code></td>
</tr>
<tr>
<td><code>body.environment</code></td>
<td>string</td>
<td>Optional</td>
<td>The identifier of the environment to start the conversation in. Only Fin for Platforms workspaces use it; other workspaces ignore it. Use the same value as <code>messenger_environment</code> in your Messenger installation. Defaults to the workspace&#39;s default environment. On a Fin for Platforms workspace, an identifier that matches no environment returns a 422 error.</td>
<td></td>
</tr>
<tr>
<td><code>body.response_format</code></td>
<td>string</td>
<td>Optional</td>
<td>The format of the <code>body</code> in Fin&#39;s replies. Defaults to <code>html</code>. Requesting <code>markdown</code> on a workspace where it is not enabled returns a 403 error.</td>
<td><code>enum: [&quot;html&quot;,&quot;markdown&quot;]; default: &quot;html&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.askfin">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "conversation_id": "ext-123",
    "message": {
      "author": "user",
      "body": "How do I reset my password?",
      "timestamp": "2025-01-24T10:01:20.000Z"
    },
    "user": {
      "id": "123456",
      "name": "John Doe",
      "email": "john.doe@example.com"
    }
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-runfinprocedure">
<summary><span>Run a Fin procedure — <code>intercom.<wbr>runfinprocedure</code></span></summary>
<p>Run <strong>Run a Fin procedure</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.runfinprocedure">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.procedure_id</code></td>
<td>string</td>
<td>Required</td>
<td>The ID of the procedure to run.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.conversation_id</code></td>
<td>string</td>
<td>Required</td>
<td>Your external conversation ID. Fin creates a conversation for this ID. If a conversation already exists for it, use <code>/fin/reply</code> instead.</td>
<td></td>
</tr>
<tr>
<td><code>body.user</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/fin_agent_user&quot;</code></td>
</tr>
<tr>
<td><code>body.message</code></td>
<td>object</td>
<td>Optional</td>
<td>Optional message posted to the conversation before the procedure runs. Only <code>body</code> is required.</td>
<td></td>
</tr>
<tr>
<td><code>body.message.body</code></td>
<td>string</td>
<td>Required</td>
<td>The body of the message.</td>
<td></td>
</tr>
<tr>
<td><code>body.message.author</code></td>
<td>string</td>
<td>Optional</td>
<td>Accepted but has no effect. The trigger message is always posted as an operator message.</td>
<td><code>enum: [&quot;user&quot;,&quot;agent&quot;,&quot;fin&quot;]</code></td>
</tr>
<tr>
<td><code>body.conversation_metadata</code></td>
<td>object</td>
<td>Optional</td>
<td>Metadata about the conversation. Only attributes are accepted (no history).</td>
<td></td>
</tr>
<tr>
<td><code>body.conversation_metadata.attributes</code></td>
<td>object</td>
<td>Optional</td>
<td>A hash of conversation attributes. Limit to 20 attributes.</td>
<td><code>maxProperties: 20; additionalProperties: true</code></td>
</tr>
<tr>
<td><code>body.environment</code></td>
<td>string</td>
<td>Optional</td>
<td>The identifier of the environment to start the conversation in. Only Fin for Platforms workspaces use it; other workspaces ignore it. Use the same value as <code>messenger_environment</code> in your Messenger installation. Defaults to the workspace&#39;s default environment. On a Fin for Platforms workspace, an identifier that matches no environment returns a 422 error.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.runfinprocedure">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "procedure_id": "12345"
  },
  "body": {
    "conversation_id": "ext-123",
    "user": {
      "id": "123456",
      "name": "John Doe",
      "email": "john.doe@example.com"
    }
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-escalatefinconversation">
<summary><span>Escalate to a human — <code>intercom.<wbr>escalatefinconversat<wbr>ion</code></span></summary>
<p>Run <strong>Escalate to a human</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.escalatefinconversation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.conversation_id</code></td>
<td>string</td>
<td>Optional</td>
<td>The external ID of the conversation to escalate. Provide this or <code>user</code>. Required on Fin for Platforms, where <code>user</code> is not supported.</td>
<td></td>
</tr>
<tr>
<td><code>body.user</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.user</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/fin_agent_user&quot;</code></td>
</tr>
<tr>
<td><code>body.user</code></td>
<td>—</td>
<td>Optional</td>
<td>The user to escalate on behalf of, creating a new conversation. Provide this or <code>conversation_id</code>. Not supported on Fin for Platforms.</td>
<td><code>allOf[2]</code></td>
</tr>
<tr>
<td><code>body.context</code></td>
<td>string</td>
<td>Optional</td>
<td>Optional background for the receiving teammate, valid with either <code>conversation_id</code> or <code>user</code>. On the Intercom Helpdesk, it appears above the summary in the internal note of the new conversation the teammate picks up, and is never shown to the end user. Not surfaced on Fin for Platforms. Avoid including credentials or unnecessary personal data — it is visible to any teammate with access to the conversation.</td>
<td><code>maxLength: 10000</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>oneOf[1]</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>oneOf[2]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.escalatefinconversation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "conversation_id": "ext-123",
    "context": "Customer is requesting a refund and is frustrated."
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listhelpcenterredirects">
<summary><span>List all redirects for a help center — <code>intercom.<wbr>listhelpcenterredire<wbr>cts</code></span></summary>
<p>Run <strong>List all redirects for a help center</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listhelpcenterredirects">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.help_center_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the help center.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to the first page.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page. Defaults to 50, maximum 250.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listhelpcenterredirects">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "help_center_id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createhelpcenterredirect">
<summary><span>Create a redirect — <code>intercom.<wbr>createhelpcenterredi<wbr>rect</code></span></summary>
<p>Run <strong>Create a redirect</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createhelpcenterredirect">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.help_center_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the help center.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_help_center_redirect_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createhelpcenterredirect">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "help_center_id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievehelpcenterredirect">
<summary><span>Retrieve a redirect — <code>intercom.<wbr>retrievehelpcenterre<wbr>direct</code></span></summary>
<p>Run <strong>Retrieve a redirect</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievehelpcenterredirect">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.help_center_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the help center.</td>
<td></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the redirect.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievehelpcenterredirect">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "help_center_id": "123",
    "id": "26"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deletehelpcenterredirect">
<summary><span>Delete a redirect — <code>intercom.<wbr>deletehelpcenterredi<wbr>rect</code></span></summary>
<p>Run <strong>Delete a redirect</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deletehelpcenterredirect">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.help_center_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the help center.</td>
<td></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the redirect.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deletehelpcenterredirect">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "help_center_id": "123",
    "id": "26"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listallcollections">
<summary><span>List all collections — <code>intercom.<wbr>listallcollections</code></span></summary>
<p>Run <strong>List all collections</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listallcollections">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to the first page.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page. Defaults to 20. Maximum is 250.</td>
<td><code>maximum: 250</code></td>
</tr>
<tr>
<td><code>query.help_center_id</code></td>
<td>integer</td>
<td>Optional</td>
<td>Only return collections that belong to this Help Center.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listallcollections">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createcollection">
<summary><span>Create a collection — <code>intercom.<wbr>createcollection</code></span></summary>
<p>Run <strong>Create a collection</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createcollection">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_collection_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createcollection">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievecollection">
<summary><span>Retrieve a collection — <code>intercom.<wbr>retrievecollection</code></span></summary>
<p>Run <strong>Retrieve a collection</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievecollection">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.collection_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the collection which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievecollection">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "collection_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatecollection">
<summary><span>Update a collection — <code>intercom.<wbr>updatecollection</code></span></summary>
<p>Run <strong>Update a collection</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatecollection">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.collection_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the collection which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_collection_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatecollection">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "collection_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deletecollection">
<summary><span>Delete a collection — <code>intercom.<wbr>deletecollection</code></span></summary>
<p>Run <strong>Delete a collection</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deletecollection">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.collection_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the collection which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deletecollection">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "collection_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievehelpcenter">
<summary><span>Retrieve a Help Center — <code>intercom.<wbr>retrievehelpcenter</code></span></summary>
<p>Run <strong>Retrieve a Help Center</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievehelpcenter">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.help_center_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the Help Center which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievehelpcenter">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "help_center_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listhelpcenters">
<summary><span>List all Help Centers — <code>intercom.<wbr>listhelpcenters</code></span></summary>
<p>Run <strong>List all Help Centers</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listhelpcenters">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listhelpcenters">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listinternalarticles">
<summary><span>List all articles — <code>intercom.<wbr>listinternalarticles</code></span></summary>
<p>Run <strong>List all articles</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listinternalarticles">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to 1.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page. Defaults to 50.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listinternalarticles">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createinternalarticle">
<summary><span>Create an internal article — <code>intercom.<wbr>createinternalarticl<wbr>e</code></span></summary>
<p>Run <strong>Create an internal article</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createinternalarticle">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_internal_article_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createinternalarticle">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrieveinternalarticle">
<summary><span>Retrieve an internal article — <code>intercom.<wbr>retrieveinternalarti<wbr>cle</code></span></summary>
<p>Run <strong>Retrieve an internal article</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrieveinternalarticle">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.internal_article_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the article which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrieveinternalarticle">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "internal_article_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updateinternalarticle">
<summary><span>Update an internal article — <code>intercom.<wbr>updateinternalarticl<wbr>e</code></span></summary>
<p>Run <strong>Update an internal article</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updateinternalarticle">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.internal_article_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the internal article which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_internal_article_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updateinternalarticle">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "internal_article_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deleteinternalarticle">
<summary><span>Delete an internal article — <code>intercom.<wbr>deleteinternalarticl<wbr>e</code></span></summary>
<p>Run <strong>Delete an internal article</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deleteinternalarticle">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.internal_article_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the internal article which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deleteinternalarticle">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "internal_article_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-attachtagtointernalarticle">
<summary><span>Add a tag to an internal article — <code>intercom.<wbr>attachtagtointernala<wbr>rticle</code></span></summary>
<p>Run <strong>Add a tag to an internal article</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.attachtagtointernalarticle">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.internal_article_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the internal article which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the tag to apply, as given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body.admin_id</code></td>
<td>string &#124; null</td>
<td>Optional</td>
<td>Optional id of the teammate to attribute the tagging to. Defaults to the authenticating teammate. Does not affect authorization.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.attachtagtointernalarticle">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "internal_article_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-detachtagfrominternalarticle">
<summary><span>Remove a tag from an internal article — <code>intercom.<wbr>detachtagfrominterna<wbr>larticle</code></span></summary>
<p>Run <strong>Remove a tag from an internal article</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.detachtagfrominternalarticle">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.internal_article_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the internal article which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the tag to remove, as given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.admin_id</code></td>
<td>string</td>
<td>Optional</td>
<td>Optional id of a teammate. The id is checked, and an unknown teammate returns a 404 <code>admin_not_found</code> error, but the removal is not recorded against the teammate.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.detachtagfrominternalarticle">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "internal_article_id": 123,
    "id": "7522907"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-searchinternalarticles">
<summary><span>Search for internal articles — <code>intercom.<wbr>searchinternalarticl<wbr>es</code></span></summary>
<p>Run <strong>Search for internal articles</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.searchinternalarticles">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.folder_id</code></td>
<td>integer</td>
<td>Optional</td>
<td>The ID of the folder to search in. Results will include articles from this folder and all its descendant folders. If omitted or blank, the response is an empty list.</td>
<td></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to 1.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page. Defaults to 10.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.searchinternalarticles">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listfolders">
<summary><span>List all folders — <code>intercom.<wbr>listfolders</code></span></summary>
<p>Run <strong>List all folders</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listfolders">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page number</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>Number of results per page</td>
<td></td>
</tr>
<tr>
<td><code>query.parent_folder_id</code></td>
<td>integer</td>
<td>Optional</td>
<td>Filter folders by parent folder ID. Use this to list only direct children of a specific folder.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listfolders">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createfolder">
<summary><span>Create a folder — <code>intercom.<wbr>createfolder</code></span></summary>
<p>Run <strong>Create a folder</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createfolder">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.folder</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.folder.name</code></td>
<td>string</td>
<td>Required</td>
<td>The name of the folder</td>
<td></td>
</tr>
<tr>
<td><code>body.folder.description</code></td>
<td>string</td>
<td>Optional</td>
<td>The description of the folder</td>
<td></td>
</tr>
<tr>
<td><code>body.folder.emoji</code></td>
<td>string</td>
<td>Optional</td>
<td>An emoji for the folder</td>
<td></td>
</tr>
<tr>
<td><code>body.folder.parent_folder_id</code></td>
<td>integer &#124; null</td>
<td>Optional</td>
<td>The ID of the parent folder</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createfolder">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievefolder">
<summary><span>Retrieve a folder — <code>intercom.<wbr>retrievefolder</code></span></summary>
<p>Run <strong>Retrieve a folder</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievefolder">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the folder</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievefolder">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 6
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatefolder">
<summary><span>Update a folder — <code>intercom.<wbr>updatefolder</code></span></summary>
<p>Run <strong>Update a folder</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatefolder">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the folder</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.folder</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.folder.name</code></td>
<td>string</td>
<td>Optional</td>
<td>The name of the folder</td>
<td></td>
</tr>
<tr>
<td><code>body.folder.description</code></td>
<td>string</td>
<td>Optional</td>
<td>The description of the folder</td>
<td></td>
</tr>
<tr>
<td><code>body.folder.emoji</code></td>
<td>string</td>
<td>Optional</td>
<td>An emoji for the folder</td>
<td></td>
</tr>
<tr>
<td><code>body.folder.parent_folder_id</code></td>
<td>integer &#124; null</td>
<td>Optional</td>
<td>The ID of the parent folder. Send <code>null</code> to move the folder to the top level. If omitted, the parent folder is unchanged.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatefolder">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 6
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deletefolder">
<summary><span>Delete a folder — <code>intercom.<wbr>deletefolder</code></span></summary>
<p>Run <strong>Delete a folder</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deletefolder">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the folder</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deletefolder">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 6
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getipallowlist">
<summary><span>Get IP allowlist settings — <code>intercom.<wbr>getipallowlist</code></span></summary>
<p>Run <strong>Get IP allowlist settings</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getipallowlist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getipallowlist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updateipallowlist">
<summary><span>Update IP allowlist settings — <code>intercom.<wbr>updateipallowlist</code></span></summary>
<p>Run <strong>Update IP allowlist settings</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updateipallowlist">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/ip_allowlist&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updateipallowlist">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createorupdatecompany">
<summary><span>Create or Update a company — <code>intercom.<wbr>createorupdatecompan<wbr>y</code></span></summary>
<p>Run <strong>Create or Update a company</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createorupdatecompany">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_or_update_company_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createorupdatecompany">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievecompany">
<summary><span>Retrieve companies — <code>intercom.<wbr>retrievecompany</code></span></summary>
<p>Run <strong>Retrieve companies</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievecompany">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.name</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>name</code> of the company to filter by.</td>
<td></td>
</tr>
<tr>
<td><code>query.company_id</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>company_id</code> of the company to filter by.</td>
<td></td>
</tr>
<tr>
<td><code>query.tag_id</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>tag_id</code> of the company to filter by.</td>
<td></td>
</tr>
<tr>
<td><code>query.segment_id</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>segment_id</code> of the company to filter by.</td>
<td></td>
</tr>
<tr>
<td><code>query.type</code></td>
<td>string</td>
<td>Optional</td>
<td>Set to <code>user</code> or <code>users</code>, together with <code>company_id</code> or <code>name</code>, to return that company&#39;s users instead of the company. The response is then a <code>user.list</code> object with a <code>users</code> array in the legacy user format, paged with <code>page</code> and <code>per_page</code> (default 50).</td>
<td><code>enum: [&quot;user&quot;,&quot;users&quot;]</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to first page</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>How many results to display per page. Defaults to 15. A value above 60 returns a <code>400</code> error with code <code>parameter_invalid</code>.</td>
<td><code>maximum: 60</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievecompany">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrieveacompanybyid">
<summary><span>Retrieve a company by ID — <code>intercom.<wbr>retrieveacompanybyid</code></span></summary>
<p>Run <strong>Retrieve a company by ID</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrieveacompanybyid">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.company_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the company which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.type</code></td>
<td>string</td>
<td>Optional</td>
<td>Set to <code>user</code> or <code>users</code> to return the company&#39;s users instead of the company. The response is then a <code>user.list</code> object with a <code>users</code> array in the legacy user format.</td>
<td><code>enum: [&quot;user&quot;,&quot;users&quot;]</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of users to fetch. Used only when <code>type</code> is <code>user</code> or <code>users</code>. Defaults to first page. There is a limit of 10,000 users; a <code>page</code> and <code>per_page</code> that go past it return a <code>400</code> error with code <code>bad_request</code>.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>How many users to return per page. Used only when <code>type</code> is <code>user</code> or <code>users</code>. Defaults to 50. A value above 60 returns a <code>400</code> error with code <code>parameter_invalid</code>.</td>
<td><code>maximum: 60</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrieveacompanybyid">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "company_id": "5f4d3c1c-7b1b-4d7d-a97e-6095715c6632"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatecompany">
<summary><span>Update a company — <code>intercom.<wbr>updatecompany</code></span></summary>
<p>Run <strong>Update a company</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatecompany">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.company_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the company which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_company_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatecompany">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "company_id": "5f4d3c1c-7b1b-4d7d-a97e-6095715c6632"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deletecompany">
<summary><span>Delete a company — <code>intercom.<wbr>deletecompany</code></span></summary>
<p>Run <strong>Delete a company</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deletecompany">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.company_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the company which is given by Intercom</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deletecompany">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "company_id": "5f4d3c1c-7b1b-4d7d-a97e-6095715c6632"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listattachedcontacts">
<summary><span>List attached contacts — <code>intercom.<wbr>listattachedcontacts</code></span></summary>
<p>Run <strong>List attached contacts</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listattachedcontacts">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.company_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the company which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>How many contacts to return per page. Defaults to 50.</td>
<td></td>
</tr>
<tr>
<td><code>query.starting_after</code></td>
<td>string</td>
<td>Optional</td>
<td>The cursor to fetch the next page of contacts. Use the <code>starting_after</code> value from <code>pages.next</code> in the previous response.</td>
<td></td>
</tr>
<tr>
<td><code>query.include_merge_history</code></td>
<td>string</td>
<td>Optional</td>
<td>Set to <code>true</code> to include each contact&#39;s <code>merge_history</code>. Any other value omits it.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listattachedcontacts">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "company_id": "5f4d3c1c-7b1b-4d7d-a97e-6095715c6632"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listattachedsegmentsforcompanies">
<summary><span>List attached segments for companies — <code>intercom.<wbr>listattachedsegments<wbr>forcompanies</code></span></summary>
<p>Run <strong>List attached segments for companies</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listattachedsegmentsforcompanies">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.company_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the company which is given by Intercom</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listattachedsegmentsforcompanies">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "company_id": "5f4d3c1c-7b1b-4d7d-a97e-6095715c6632"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listcompanynotes">
<summary><span>List all company notes — <code>intercom.<wbr>listcompanynotes</code></span></summary>
<p>Run <strong>List all company notes</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listcompanynotes">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.company_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the company which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to return. Defaults to <code>1</code>.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of notes to return per page. Defaults to <code>50</code>, maximum <code>60</code>.</td>
<td></td>
</tr>
<tr>
<td><code>query.order</code></td>
<td>string</td>
<td>Optional</td>
<td>The order the notes are returned in, by id. Defaults to <code>desc</code>.</td>
<td><code>enum: [&quot;asc&quot;,&quot;desc&quot;]</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listcompanynotes">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "company_id": "5f4d3c1c-7b1b-4d7d-a97e-6095715c6632"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createcompanynote">
<summary><span>Create a company note — <code>intercom.<wbr>createcompanynote</code></span></summary>
<p>Run <strong>Create a company note</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createcompanynote">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.company_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the company which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.body</code></td>
<td>string</td>
<td>Required</td>
<td>The text of the note.</td>
<td></td>
</tr>
<tr>
<td><code>body.admin_id</code></td>
<td>string</td>
<td>Optional</td>
<td>The unique identifier of the admin creating the note. If not provided, defaults to the admin associated with the access token.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createcompanynote">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "company_id": "5f4d3c1c-7b1b-4d7d-a97e-6095715c6632"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-searchcompanies">
<summary><span>Search companies — <code>intercom.<wbr>searchcompanies</code></span></summary>
<p>Run <strong>Search companies</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.searchcompanies">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/company_search_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.searchcompanies">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listallcompanies">
<summary><span>List all companies — <code>intercom.<wbr>listallcompanies</code></span></summary>
<p>Run <strong>List all companies</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listallcompanies">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to first page</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>How many results to return per page. Defaults to 15. A value above 60 returns a <code>400</code> error with code <code>parameter_invalid</code>.</td>
<td><code>maximum: 60</code></td>
</tr>
<tr>
<td><code>query.order</code></td>
<td>string</td>
<td>Optional</td>
<td><code>asc</code> or <code>desc</code>. Return the companies in ascending or descending order. Defaults to desc. Any other value returns a <code>400</code> error with code <code>parameter_invalid</code>.</td>
<td><code>enum: [&quot;asc&quot;,&quot;desc&quot;]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listallcompanies">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-scrolloverallcompanies">
<summary><span>Scroll over all companies — <code>intercom.<wbr>scrolloverallcompani<wbr>es</code></span></summary>
<p>Run <strong>Scroll over all companies</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.scrolloverallcompanies">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.scroll_param</code></td>
<td>string</td>
<td>Optional</td>
<td>The <code>scroll_param</code> from the previous response. Omit it to start a new scroll.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.scrolloverallcompanies">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-attachcontacttoacompany">
<summary><span>Attach a Contact to a Company — <code>intercom.<wbr>attachcontacttoacomp<wbr>any</code></span></summary>
<p>Run <strong>Attach a Contact to a Company</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.attachcontacttoacompany">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the contact which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the company which is given by Intercom</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.attachcontacttoacompany">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "58a430d35458202d41b1e65b"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listcompaniesforacontact">
<summary><span>List attached companies for contact — <code>intercom.<wbr>listcompaniesforacon<wbr>tact</code></span></summary>
<p>Run <strong>List attached companies for contact</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listcompaniesforacontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the contact which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Values below 1 are treated as 1.</td>
<td><code>default: 1</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of companies to return per page. The maximum is 60; a value above 60 returns a <code>400</code> error with code <code>parameter_invalid</code>.</td>
<td><code>default: 50; maximum: 60</code></td>
</tr>
<tr>
<td><code>query.order</code></td>
<td>string</td>
<td>Optional</td>
<td>The order of the companies by when they were last active (<code>last_request_at</code>). The value is case-insensitive, and any value other than <code>asc</code> is treated as <code>desc</code>.</td>
<td><code>enum: [&quot;asc&quot;,&quot;desc&quot;]; default: &quot;desc&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listcompaniesforacontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "63a07ddf05a32042dffac965"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-detachcontactfromacompany">
<summary><span>Detach a contact from a company — <code>intercom.<wbr>detachcontactfromaco<wbr>mpany</code></span></summary>
<p>Run <strong>Detach a contact from a company</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.detachcontactfromacompany">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the contact which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>path.company_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the company which is given by Intercom</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.detachcontactfromacompany">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "58a430d35458202d41b1e65b",
    "company_id": "58a430d35458202d41b1e65b"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listnotes">
<summary><span>List all notes — <code>intercom.<wbr>listnotes</code></span></summary>
<p>Run <strong>List all notes</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listnotes">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of a contact.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to return. Defaults to <code>1</code>.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of notes to return per page. Defaults to <code>50</code>, maximum <code>60</code>.</td>
<td></td>
</tr>
<tr>
<td><code>query.order</code></td>
<td>string</td>
<td>Optional</td>
<td>The order the notes are returned in, by id. Defaults to <code>desc</code>.</td>
<td><code>enum: [&quot;asc&quot;,&quot;desc&quot;]</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listnotes">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createnote">
<summary><span>Create a note — <code>intercom.<wbr>createnote</code></span></summary>
<p>Run <strong>Create a note</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createnote">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of a given contact.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.body</code></td>
<td>string</td>
<td>Required</td>
<td>The text of the note.</td>
<td></td>
</tr>
<tr>
<td><code>body.admin_id</code></td>
<td>string</td>
<td>Optional</td>
<td>The unique identifier of a given admin.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createnote">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "6762f0ad1bb69f9f2193bb62"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listsegmentsforacontact">
<summary><span>List attached segments for contact — <code>intercom.<wbr>listsegmentsforacont<wbr>act</code></span></summary>
<p>Run <strong>List attached segments for contact</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listsegmentsforacontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the contact which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listsegmentsforacontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "63a07ddf05a32042dffac965"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listsubscriptionsforacontact">
<summary><span>List subscriptions for a contact — <code>intercom.<wbr>listsubscriptionsfor<wbr>acontact</code></span></summary>
<p>Run <strong>List subscriptions for a contact</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listsubscriptionsforacontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the contact which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listsubscriptionsforacontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "63a07ddf05a32042dffac965"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-attachsubscriptiontypetocontact">
<summary><span>Add subscription to a contact — <code>intercom.<wbr>attachsubscriptionty<wbr>petocontact</code></span></summary>
<p>Run <strong>Add subscription to a contact</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.attachsubscriptiontypetocontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the contact which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the subscription which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>body.consent_type</code></td>
<td>string</td>
<td>Optional</td>
<td>Ignored. Whether the contact is opted in or out is decided by the subscription type&#39;s own <code>consent_type</code>, not by this value.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.attachsubscriptiontypetocontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "63a07ddf05a32042dffac965"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-detachsubscriptiontypetocontact">
<summary><span>Remove subscription from a contact — <code>intercom.<wbr>detachsubscriptionty<wbr>petocontact</code></span></summary>
<p>Run <strong>Remove subscription from a contact</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.detachsubscriptiontypetocontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the contact which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>path.subscription_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the subscription type which is given by Intercom</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.detachsubscriptiontypetocontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "63a07ddf05a32042dffac965",
    "subscription_id": "37846"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listtagsforacontact">
<summary><span>List tags attached to a contact — <code>intercom.<wbr>listtagsforacontact</code></span></summary>
<p>Run <strong>List tags attached to a contact</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listtagsforacontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the contact which is given by Intercom</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listtagsforacontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "63a07ddf05a32042dffac965"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-attachtagtocontact">
<summary><span>Add tag to a contact — <code>intercom.<wbr>attachtagtocontact</code></span></summary>
<p>Run <strong>Add tag to a contact</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.attachtagtocontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the contact which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the tag which is given by Intercom</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.attachtagtocontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "63a07ddf05a32042dffac965"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-detachtagfromcontact">
<summary><span>Remove tag from a contact — <code>intercom.<wbr>detachtagfromcontact</code></span></summary>
<p>Run <strong>Remove tag from a contact</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.detachtagfromcontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the contact which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>path.tag_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the tag which is given by Intercom</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.detachtagfromcontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "63a07ddf05a32042dffac965",
    "tag_id": "7522907"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listdeletedcontacts">
<summary><span>List deleted contacts — <code>intercom.<wbr>listdeletedcontacts</code></span></summary>
<p>Run <strong>List deleted contacts</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listdeletedcontacts">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results per page. Defaults to <code>10</code>, with a maximum of <code>150</code>; larger values are treated as <code>150</code>. Only the leading digits are read, so <code>1.5</code> is treated as <code>1</code>. A value that doesn&#39;t start with a positive integer, such as <code>0</code> or <code>abc</code>, returns a <code>400</code> error with code <code>invalid_per_page</code>.</td>
<td><code>default: 10; minimum: 1; maximum: 150</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to <code>1</code>.</td>
<td><code>default: 1; minimum: 1</code></td>
</tr>
<tr>
<td><code>query.escape_identity</code></td>
<td>boolean</td>
<td>Optional</td>
<td>By default, <code>email</code> values in the response are HTML-escaped (for example, <code>&amp;amp;</code> is returned as <code>&amp;amp;amp;</code>). Pass <code>false</code> to return them unescaped.</td>
<td><code>default: true</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listdeletedcontacts">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatecontact">
<summary><span>Update a contact — <code>intercom.<wbr>updatecontact</code></span></summary>
<p>Run <strong>Update a contact</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatecontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>id</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include_merge_history</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Pass <code>true</code> to include the contact&#39;s merge history in the response. Returned for contacts of any role, with at most the 10 most recent merges.</td>
<td><code>default: false</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>oneOf[1]; $ref: &quot;#/definitions/update_contact_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatecontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "63a07ddf05a32042dffac965"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-showcontact">
<summary><span>Get a contact — <code>intercom.<wbr>showcontact</code></span></summary>
<p>Run <strong>Get a contact</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.showcontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>contact_id</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include_merge_history</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Pass <code>true</code> to include the contact&#39;s merge history in the response. Returned for contacts of any role, with at most the 10 most recent merges.</td>
<td><code>default: false</code></td>
</tr>
<tr>
<td><code>query.escape_identity</code></td>
<td>boolean</td>
<td>Optional</td>
<td>By default, <code>name</code> and <code>email</code> values in the response, including nested ones such as social profile names, are HTML-escaped (for example, <code>&amp;amp;</code> is returned as <code>&amp;amp;amp;</code>). Custom attributes and tags are never escaped. Pass <code>false</code> to return them unescaped.</td>
<td><code>default: true</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.showcontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "63a07ddf05a32042dffac965"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deletecontact">
<summary><span>Delete a contact — <code>intercom.<wbr>deletecontact</code></span></summary>
<p>Run <strong>Delete a contact</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deletecontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>contact_id</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deletecontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-mergecontact">
<summary><span>Merge a lead and a user — <code>intercom.<wbr>mergecontact</code></span></summary>
<p>Run <strong>Merge a lead and a user</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.mergecontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include_merge_history</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Pass <code>true</code> to include the merge history of the resulting contact in the response, with at most the 10 most recent merges.</td>
<td><code>default: false</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/merge_contacts_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.mergecontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-previewmergecontact">
<summary><span>Preview a contact merge — <code>intercom.<wbr>previewmergecontact</code></span></summary>
<p>Run <strong>Preview a contact merge</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.previewmergecontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/merge_preview_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.previewmergecontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-searchcontacts">
<summary><span>Search contacts — <code>intercom.<wbr>searchcontacts</code></span></summary>
<p>Run <strong>Search contacts</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.searchcontacts">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include_merge_history</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Pass <code>true</code> in the query string to include a <code>merge_history</code> array on each contact in the response; a JSON boolean in the request body is ignored. Returned for contacts of any role, with at most the 10 most recent merges.</td>
<td><code>default: false</code></td>
</tr>
<tr>
<td><code>query.escape_identity</code></td>
<td>boolean</td>
<td>Optional</td>
<td>By default, <code>name</code> and <code>email</code> values in the response, including nested ones such as social profile names, are HTML-escaped (for example, <code>&amp;amp;</code> is returned as <code>&amp;amp;amp;</code>). Custom attributes and tags are never escaped. Pass <code>false</code> to return them unescaped.</td>
<td><code>default: true</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/contact_search_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.searchcontacts">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listcontactactivities">
<summary><span>List all contact activities — <code>intercom.<wbr>listcontactactivitie<wbr>s</code></span></summary>
<p>Run <strong>List all contact activities</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listcontactactivities">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page. Defaults to 50, minimum 1, maximum 150; larger values are treated as <code>150</code>. Only the leading digits are read, so <code>1.5</code> is treated as <code>1</code>. A value that doesn&#39;t start with a positive integer, such as <code>0</code> or <code>abc</code>, returns a <code>400</code> error with code <code>invalid_per_page</code>.</td>
<td><code>default: 50; minimum: 1; maximum: 150</code></td>
</tr>
<tr>
<td><code>query.starting_after</code></td>
<td>string</td>
<td>Optional</td>
<td>The cursor value from <code>pages.next.starting_after</code> in a previous response. Used to paginate through results.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listcontactactivities">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listcontacts">
<summary><span>List all contacts — <code>intercom.<wbr>listcontacts</code></span></summary>
<p>Run <strong>List all contacts</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listcontacts">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include_merge_history</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Pass <code>true</code> to include a <code>merge_history</code> array on each contact in the response. Returned for contacts of any role, with at most the 10 most recent merges.</td>
<td><code>default: false</code></td>
</tr>
<tr>
<td><code>query.escape_identity</code></td>
<td>boolean</td>
<td>Optional</td>
<td>By default, <code>name</code> and <code>email</code> values in the response, including nested ones such as social profile names, are HTML-escaped (for example, <code>&amp;amp;</code> is returned as <code>&amp;amp;amp;</code>). Custom attributes and tags are never escaped. Pass <code>false</code> to return them unescaped.</td>
<td><code>default: true</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results per page. Defaults to <code>10</code>, with a maximum of <code>150</code>; larger values are treated as <code>150</code>. Only the leading digits are read, so <code>1.5</code> is treated as <code>1</code>. A value that doesn&#39;t start with a positive integer, such as <code>0</code> or <code>abc</code>, returns a <code>400</code> error with code <code>invalid_per_page</code>.</td>
<td><code>default: 10; minimum: 1; maximum: 150</code></td>
</tr>
<tr>
<td><code>query.starting_after</code></td>
<td>string</td>
<td>Optional</td>
<td>The cursor value from <code>pages.next.starting_after</code> in a previous response. An empty value is ignored. A value that isn&#39;t a valid cursor returns a <code>400</code> error with code <code>client_error</code>.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listcontacts">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createcontact">
<summary><span>Create contact — <code>intercom.<wbr>createcontact</code></span></summary>
<p>Run <strong>Create contact</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createcontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>oneOf[1]; $ref: &quot;#/definitions/create_contact_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createcontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-showcontactbyexternalid">
<summary><span>Get a contact by External ID — <code>intercom.<wbr>showcontactbyexterna<wbr>lid</code></span></summary>
<p>Run <strong>Get a contact by External ID</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.showcontactbyexternalid">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.external_id</code></td>
<td>string</td>
<td>Required</td>
<td>The external ID of the user that you want to retrieve</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include_merge_history</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Pass <code>true</code> to include the contact&#39;s merge history in the response. Returned for contacts of any role, with at most the 10 most recent merges.</td>
<td><code>default: false</code></td>
</tr>
<tr>
<td><code>query.escape_identity</code></td>
<td>boolean</td>
<td>Optional</td>
<td>By default, <code>name</code> and <code>email</code> values in the response, including nested ones such as social profile names, are HTML-escaped (for example, <code>&amp;amp;</code> is returned as <code>&amp;amp;amp;</code>). Custom attributes and tags are never escaped. Pass <code>false</code> to return them unescaped.</td>
<td><code>default: true</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.showcontactbyexternalid">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "external_id": "cdd29344-5e0c-4ef0-ac56-f9ba2979bc27"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-archivecontact">
<summary><span>Archive contact — <code>intercom.<wbr>archivecontact</code></span></summary>
<p>Run <strong>Archive contact</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.archivecontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>contact_id</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.archivecontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "63a07ddf05a32042dffac965"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-unarchivecontact">
<summary><span>Unarchive contact — <code>intercom.<wbr>unarchivecontact</code></span></summary>
<p>Run <strong>Unarchive contact</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.unarchivecontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>contact_id</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.unarchivecontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "63a07ddf05a32042dffac965"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listcontactbanners">
<summary><span>List banners for a contact — <code>intercom.<wbr>listcontactbanners</code></span></summary>
<p>Run <strong>List banners for a contact</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listcontactbanners">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of a contact.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listcontactbanners">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-dismisscontactbanner">
<summary><span>Dismiss a banner for a contact — <code>intercom.<wbr>dismisscontactbanner</code></span></summary>
<p>Run <strong>Dismiss a banner for a contact</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.dismisscontactbanner">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of a contact.</td>
<td></td>
</tr>
<tr>
<td><code>path.view_id</code></td>
<td>string</td>
<td>Required</td>
<td>The <code>view_id</code> of the banner to dismiss, as returned by the list banners endpoint.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.dismisscontactbanner">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example",
    "view_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-blockcontact">
<summary><span>Block contact — <code>intercom.<wbr>blockcontact</code></span></summary>
<p>Run <strong>Block contact</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.blockcontact">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>contact_id</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.blockcontact">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "contact_id": "63a07ddf05a32042dffac965"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listcontactmergehistory">
<summary><span>Get contact merge history — <code>intercom.<wbr>listcontactmergehist<wbr>ory</code></span></summary>
<p>Run <strong>Get contact merge history</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listcontactmergehistory">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The id of the contact to fetch merge history for.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.cursor</code></td>
<td>string</td>
<td>Optional</td>
<td>A cursor for pagination. Pass the <code>next_cursor</code> value from a previous response to fetch the next page.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page (default 50, max 150). A value outside 1–150 returns a <code>422</code> error.</td>
<td><code>default: 50; minimum: 1; maximum: 150</code></td>
</tr>
<tr>
<td><code>query.order</code></td>
<td>string</td>
<td>Optional</td>
<td>The order to return results in. Defaults to descending. Any other value returns a <code>422</code> error.</td>
<td><code>enum: [&quot;asc&quot;,&quot;desc&quot;]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listcontactmergehistory">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "63a07ddf05a32042dffac965"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-bulkcreatecontacts">
<summary><span>Bulk create contacts — <code>intercom.<wbr>bulkcreatecontacts</code></span></summary>
<p>Run <strong>Bulk create contacts</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.bulkcreatecontacts">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/bulk_create_contacts_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.bulkcreatecontacts">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-bulkupdatecontacts">
<summary><span>Bulk update contacts — <code>intercom.<wbr>bulkupdatecontacts</code></span></summary>
<p>Run <strong>Bulk update contacts</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.bulkupdatecontacts">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/bulk_update_contacts_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.bulkupdatecontacts">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-bulkdeletecontacts">
<summary><span>Bulk delete contacts — <code>intercom.<wbr>bulkdeletecontacts</code></span></summary>
<p>Run <strong>Bulk delete contacts</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.bulkdeletecontacts">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/bulk_delete_contacts_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.bulkdeletecontacts">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-showbulkupdatecontactsjob">
<summary><span>Get a bulk update job — <code>intercom.<wbr>showbulkupdatecontac<wbr>tsjob</code></span></summary>
<p>Run <strong>Get a bulk update job</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.showbulkupdatecontactsjob">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the bulk job.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.showbulkupdatecontactsjob">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "job_v2_1"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-bulkcontentactions">
<summary><span>Run a bulk action on Knowledge Hub content — <code>intercom.<wbr>bulkcontentactions</code></span></summary>
<p>Run <strong>Run a bulk action on Knowledge Hub content</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.bulkcontentactions">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/content_bulk_action_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.bulkcontentactions">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "action": "publish",
    "content_ids": []
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-searchcontent">
<summary><span>Search knowledge base contents — <code>intercom.<wbr>searchcontent</code></span></summary>
<p>Run <strong>Search knowledge base contents</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.searchcontent">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.query</code></td>
<td>string</td>
<td>Optional</td>
<td>A free-text search term matched against the title and body of each content item. When omitted, returns the most recent content items. Keep it to 500 characters or fewer. The API doesn&#39;t currently reject longer values.</td>
<td><code>maxLength: 500</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page number to fetch. Defaults to 1. Values below 1 are clamped to 1. Values above 5001 return a <code>400</code> <code>parameter_invalid</code> error.</td>
<td><code>default: 1; minimum: 1</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>Number of results per page. Defaults to 10. Maximum 50.</td>
<td><code>default: 10; minimum: 1; maximum: 50</code></td>
</tr>
<tr>
<td><code>query.states</code></td>
<td>array</td>
<td>Optional</td>
<td>Filter by publication state. Accepts a comma-separated list or repeated params.</td>
<td></td>
</tr>
<tr>
<td><code>query.states[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;published&quot;,&quot;draft&quot;]</code></td>
</tr>
<tr>
<td><code>query.locales</code></td>
<td>array</td>
<td>Optional</td>
<td>Filter by locale codes (e.g. <code>en</code>, <code>fr</code>, <code>de</code>). Accepts a comma-separated list or repeated params.</td>
<td></td>
</tr>
<tr>
<td><code>query.locales[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.tag_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>Filter by tag IDs. Pairs with <code>tag_operator</code> to control match semantics. Accepts a comma-separated list or repeated params.</td>
<td></td>
</tr>
<tr>
<td><code>query.tag_ids[]</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.tag_operator</code></td>
<td>string</td>
<td>Optional</td>
<td>Match operator paired with <code>tag_ids</code>. <code>IN</code> returns content matching any of the given tags; <code>NIN</code> excludes content matching any of them.</td>
<td><code>enum: [&quot;IN&quot;,&quot;NIN&quot;]</code></td>
</tr>
<tr>
<td><code>query.any_tag_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>Filter by tag IDs using OR semantics — returns content matching any of the given tags. Alternative to <code>tag_ids</code> + <code>tag_operator</code>. Accepts a comma-separated list or repeated params.</td>
<td></td>
</tr>
<tr>
<td><code>query.any_tag_ids[]</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.folder_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>Filter by folder IDs. Must be sent together with <code>folder_entity_type</code>. Accepts a comma-separated list or repeated params.</td>
<td></td>
</tr>
<tr>
<td><code>query.folder_ids[]</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.folder_entity_type</code></td>
<td>string</td>
<td>Optional</td>
<td>Required when <code>folder_ids</code> is provided. Identifies the entity type the folder IDs refer to.</td>
<td><code>enum: [&quot;folder&quot;]</code></td>
</tr>
<tr>
<td><code>query.content_types</code></td>
<td>array</td>
<td>Optional</td>
<td>Restrict the search to specific content types. When provided, this REPLACES the default content type set rather than filtering on top of it. Accepts a comma-separated list or repeated params.</td>
<td></td>
</tr>
<tr>
<td><code>query.content_types[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;snippet&quot;,&quot;external_content&quot;,&quot;file_source_content&quot;,&quot;internal_article&quot;,&quot;article&quot;]</code></td>
</tr>
<tr>
<td><code>query.copilot_state</code></td>
<td>string</td>
<td>Optional</td>
<td>Filter by whether the content is enabled for Copilot.</td>
<td><code>enum: [&quot;on&quot;,&quot;off&quot;]</code></td>
</tr>
<tr>
<td><code>query.fin_service_state</code></td>
<td>string</td>
<td>Optional</td>
<td>Filter by whether the content is enabled for Fin AI Agent (customer-facing service).</td>
<td><code>enum: [&quot;on&quot;,&quot;off&quot;]</code></td>
</tr>
<tr>
<td><code>query.fin_sales_state</code></td>
<td>string</td>
<td>Optional</td>
<td>Filter by whether the content is enabled for Fin Sales Agent.</td>
<td><code>enum: [&quot;on&quot;,&quot;off&quot;]</code></td>
</tr>
<tr>
<td><code>query.created_by_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>Filter by the admin IDs that created the content. Accepts a comma-separated list or repeated params.</td>
<td></td>
</tr>
<tr>
<td><code>query.created_by_ids[]</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.last_updated_by_ids</code></td>
<td>array</td>
<td>Optional</td>
<td>Filter by the admin IDs that last updated the content. Accepts a comma-separated list or repeated params.</td>
<td></td>
</tr>
<tr>
<td><code>query.last_updated_by_ids[]</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.created_at_after</code></td>
<td>integer</td>
<td>Optional</td>
<td>Return content created at or after this time. Unix epoch seconds.</td>
<td></td>
</tr>
<tr>
<td><code>query.created_at_before</code></td>
<td>integer</td>
<td>Optional</td>
<td>Return content created at or before this time. Unix epoch seconds.</td>
<td></td>
</tr>
<tr>
<td><code>query.updated_at_after</code></td>
<td>integer</td>
<td>Optional</td>
<td>Return content last updated at or after this time. Unix epoch seconds.</td>
<td></td>
</tr>
<tr>
<td><code>query.updated_at_before</code></td>
<td>integer</td>
<td>Optional</td>
<td>Return content last updated at or before this time. Unix epoch seconds.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.searchcontent">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listcontentsnippets">
<summary><span>List all content snippets — <code>intercom.<wbr>listcontentsnippets</code></span></summary>
<p>Run <strong>List all content snippets</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listcontentsnippets">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page. Max value of 50.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listcontentsnippets">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createcontentsnippet">
<summary><span>Create a content snippet — <code>intercom.<wbr>createcontentsnippet</code></span></summary>
<p>Run <strong>Create a content snippet</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createcontentsnippet">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/content_snippet_create_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createcontentsnippet">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "title": "How to reset your password"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getcontentsnippet">
<summary><span>Retrieve a content snippet — <code>intercom.<wbr>getcontentsnippet</code></span></summary>
<p>Run <strong>Retrieve a content snippet</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getcontentsnippet">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the content snippet.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getcontentsnippet">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatecontentsnippet">
<summary><span>Update a content snippet — <code>intercom.<wbr>updatecontentsnippet</code></span></summary>
<p>Run <strong>Update a content snippet</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatecontentsnippet">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the content snippet.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/content_snippet_update_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatecontentsnippet">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  },
  "body": {}
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deletecontentsnippet">
<summary><span>Delete a content snippet — <code>intercom.<wbr>deletecontentsnippet</code></span></summary>
<p>Run <strong>Delete a content snippet</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deletecontentsnippet">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the content snippet.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deletecontentsnippet">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-attachtagtocontentsnippet">
<summary><span>Add a tag to a content snippet — <code>intercom.<wbr>attachtagtocontentsn<wbr>ippet</code></span></summary>
<p>Run <strong>Add a tag to a content snippet</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.attachtagtocontentsnippet">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.content_snippet_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the content snippet.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the tag to apply, as given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body.admin_id</code></td>
<td>string &#124; null</td>
<td>Optional</td>
<td>Optional id of the teammate to attribute the tagging to. Defaults to the authenticating teammate. Does not affect authorization.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.attachtagtocontentsnippet">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "content_snippet_id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-detachtagfromcontentsnippet">
<summary><span>Remove a tag from a content snippet — <code>intercom.<wbr>detachtagfromcontent<wbr>snippet</code></span></summary>
<p>Run <strong>Remove a tag from a content snippet</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.detachtagfromcontentsnippet">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.content_snippet_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the content snippet.</td>
<td></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the tag to remove, as given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.admin_id</code></td>
<td>string</td>
<td>Optional</td>
<td>Optional id of a teammate. The id is checked, and an unknown teammate returns a 404 <code>admin_not_found</code> error, but the removal is not recorded against the teammate.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.detachtagfromcontentsnippet">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "content_snippet_id": "123",
    "id": "7522907"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listdynamiccontents">
<summary><span>List all dynamic content — <code>intercom.<wbr>listdynamiccontents</code></span></summary>
<p>Run <strong>List all dynamic content</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listdynamiccontents">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to the first page. Values below 1 are treated as 1.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page. Defaults to 50. Values above 50 are reduced to 50, and values below 1 are treated as 1.</td>
<td><code>maximum: 50</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listdynamiccontents">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createdynamiccontent">
<summary><span>Create dynamic content — <code>intercom.<wbr>createdynamiccontent</code></span></summary>
<p>Run <strong>Create dynamic content</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createdynamiccontent">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/dynamic_content_create_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createdynamiccontent">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "name": "Support phone number",
    "content_type": "inline",
    "default_locale": "en",
    "variations": [
      {
        "locale": "en"
      }
    ]
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getdynamiccontent">
<summary><span>Retrieve dynamic content — <code>intercom.<wbr>getdynamiccontent</code></span></summary>
<p>Run <strong>Retrieve dynamic content</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getdynamiccontent">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the dynamic content.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getdynamiccontent">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatedynamiccontent">
<summary><span>Update dynamic content — <code>intercom.<wbr>updatedynamiccontent</code></span></summary>
<p>Run <strong>Update dynamic content</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatedynamiccontent">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the dynamic content.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/dynamic_content_update_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatedynamiccontent">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  },
  "body": {}
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deletedynamiccontent">
<summary><span>Delete dynamic content — <code>intercom.<wbr>deletedynamiccontent</code></span></summary>
<p>Run <strong>Delete dynamic content</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deletedynamiccontent">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the dynamic content.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deletedynamiccontent">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-attachtagtoconversation">
<summary><span>Add tag to a conversation — <code>intercom.<wbr>attachtagtoconversat<wbr>ion</code></span></summary>
<p>Run <strong>Add tag to a conversation</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.attachtagtoconversation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.conversation_id</code></td>
<td>string</td>
<td>Required</td>
<td>conversation_id</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the tag which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>body.admin_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the admin which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.attachtagtoconversation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "conversation_id": "64619700005694"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-detachtagfromconversation">
<summary><span>Remove tag from a conversation — <code>intercom.<wbr>detachtagfromconvers<wbr>ation</code></span></summary>
<p>Run <strong>Remove tag from a conversation</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.detachtagfromconversation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.conversation_id</code></td>
<td>string</td>
<td>Required</td>
<td>conversation_id</td>
<td></td>
</tr>
<tr>
<td><code>path.tag_id</code></td>
<td>string</td>
<td>Required</td>
<td>tag_id</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.admin_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the admin which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.detachtagfromconversation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "conversation_id": "64619700005694",
    "tag_id": "7522907"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listconversations">
<summary><span>List all conversations — <code>intercom.<wbr>listconversations</code></span></summary>
<p>Run <strong>List all conversations</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listconversations">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>How many results per page</td>
<td><code>default: 20; maximum: 150</code></td>
</tr>
<tr>
<td><code>query.starting_after</code></td>
<td>string</td>
<td>Optional</td>
<td>String used to get the next page of conversations.</td>
<td></td>
</tr>
<tr>
<td><code>query.include_monitors</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If set to true, the response will include a <code>monitor_evaluations</code> array on each conversation with the latest QA monitor evaluation for each monitor that has evaluated it.</td>
<td><code>default: false</code></td>
</tr>
<tr>
<td><code>query.include_scorecards</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If set to true, the response will include a <code>scorecards</code> array on each conversation with any QA scorecard results.</td>
<td><code>default: false</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listconversations">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createconversation">
<summary><span>Creates a conversation — <code>intercom.<wbr>createconversation</code></span></summary>
<p>Run <strong>Creates a conversation</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createconversation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_conversation_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createconversation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrieveconversation">
<summary><span>Retrieve a conversation — <code>intercom.<wbr>retrieveconversation</code></span></summary>
<p>Run <strong>Retrieve a conversation</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrieveconversation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.conversation_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The id of the conversation to target</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.display_as</code></td>
<td>string</td>
<td>Optional</td>
<td>Set to plaintext to retrieve conversation messages in plain text. This affects both the body and subject fields. Inline links are rendered as <code>label (url)</code>, preserving the link URL alongside the visible text.</td>
<td></td>
</tr>
<tr>
<td><code>query.include_translations</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If set to true, conversation parts will be translated to the detected language of the conversation.</td>
<td></td>
</tr>
<tr>
<td><code>query.include_email_history</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If set to true, the source of the conversation will include the email history, for conversations started by email.</td>
<td></td>
</tr>
<tr>
<td><code>query.parts_created_after</code></td>
<td>integer</td>
<td>Optional</td>
<td>Only include conversation parts created at or after this time, as a Unix timestamp in seconds.</td>
<td></td>
</tr>
<tr>
<td><code>query.parts_created_before</code></td>
<td>integer</td>
<td>Optional</td>
<td>Only include conversation parts created at or before this time, as a Unix timestamp in seconds.</td>
<td></td>
</tr>
<tr>
<td><code>query.include_monitors</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If set to true, the response will include a <code>monitor_evaluations</code> array with the latest QA monitor evaluation for each monitor that has evaluated this conversation.</td>
<td><code>default: false</code></td>
</tr>
<tr>
<td><code>query.include_scorecards</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If set to true, the response will include a <code>scorecards</code> array with any QA scorecard results for this conversation.</td>
<td><code>default: false</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrieveconversation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "conversation_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updateconversation">
<summary><span>Update a conversation — <code>intercom.<wbr>updateconversation</code></span></summary>
<p>Run <strong>Update a conversation</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updateconversation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.conversation_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The id of the conversation to target</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.display_as</code></td>
<td>string</td>
<td>Optional</td>
<td>Set to plaintext to retrieve conversation messages in plain text. This affects both the body and subject fields. Inline links are rendered as <code>label (url)</code>, preserving the link URL alongside the visible text.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_conversation_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updateconversation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "conversation_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deleteconversation">
<summary><span>Delete a conversation — <code>intercom.<wbr>deleteconversation</code></span></summary>
<p>Run <strong>Delete a conversation</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deleteconversation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.conversation_id</code></td>
<td>integer</td>
<td>Required</td>
<td>id</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.retain_metrics</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If true (default), deletes the conversation while retaining reporting data. If false, deletes the conversation and all associated reporting data. Setting to false requires the <code>delete_conversations_and_metrics</code> OAuth scope.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deleteconversation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "conversation_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-searchconversations">
<summary><span>Search conversations — <code>intercom.<wbr>searchconversations</code></span></summary>
<p>Run <strong>Search conversations</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.searchconversations">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include_monitors</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If set to true, the response will include a <code>monitor_evaluations</code> array on each conversation with the latest QA monitor evaluation for each monitor that has evaluated it.</td>
<td><code>default: false</code></td>
</tr>
<tr>
<td><code>query.include_scorecards</code></td>
<td>boolean</td>
<td>Optional</td>
<td>If set to true, the response will include a <code>scorecards</code> array on each conversation with any QA scorecard results.</td>
<td><code>default: false</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/search_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.searchconversations">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-replyconversation">
<summary><span>Reply to a conversation — <code>intercom.<wbr>replyconversation</code></span></summary>
<p>Run <strong>Reply to a conversation</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.replyconversation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.conversation_id</code></td>
<td>string</td>
<td>Required</td>
<td>The Intercom provisioned identifier for the conversation, or the string <code>last</code> to use the most recent conversation of a contact. With <code>last</code>, also send the contact&#39;s <code>intercom_user_id</code>, <code>user_id</code> or <code>email</code> in the request body, whatever type of request you send. A contact that can&#39;t be found returns a <code>404</code> error, and a contact with no conversations returns a <code>422</code> error.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/reply_conversation_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.replyconversation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "conversation_id": "123 or \"last\""
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-manageconversation">
<summary><span>Manage a conversation — <code>intercom.<wbr>manageconversation</code></span></summary>
<p>Run <strong>Manage a conversation</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.manageconversation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.conversation_id</code></td>
<td>string</td>
<td>Required</td>
<td>The identifier for the conversation as given by Intercom, or the string <code>last</code> to use the most recent conversation of a contact. With <code>last</code>, also send the contact&#39;s <code>intercom_user_id</code>, <code>user_id</code> or <code>email</code> in the request body, whatever type of request you send. A contact that can&#39;t be found returns a <code>404</code> error, and a contact with no conversations returns a <code>422</code> error.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>oneOf[1]; $ref: &quot;#/definitions/close_conversation_request&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>oneOf[2]; $ref: &quot;#/definitions/snooze_conversation_request&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>oneOf[3]; $ref: &quot;#/definitions/open_conversation_request&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>oneOf[4]; $ref: &quot;#/definitions/assign_conversation_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.manageconversation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "conversation_id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-attachcontacttoconversation">
<summary><span>Attach a contact to a conversation — <code>intercom.<wbr>attachcontacttoconve<wbr>rsation</code></span></summary>
<p>Run <strong>Attach a contact to a conversation</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.attachcontacttoconversation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.conversation_id</code></td>
<td>string</td>
<td>Required</td>
<td>The identifier for the conversation as given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/attach_contact_to_conversation_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.attachcontacttoconversation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "conversation_id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-detachcontactfromconversation">
<summary><span>Detach a contact from a group conversation — <code>intercom.<wbr>detachcontactfromcon<wbr>versation</code></span></summary>
<p>Run <strong>Detach a contact from a group conversation</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.detachcontactfromconversation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.conversation_id</code></td>
<td>string</td>
<td>Required</td>
<td>The identifier for the conversation as given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>path.contact_id</code></td>
<td>string</td>
<td>Required</td>
<td>The identifier for the contact as given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/detach_contact_from_conversation_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.detachcontactfromconversation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "conversation_id": "123",
    "contact_id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listhandlingevents">
<summary><span>List handling events — <code>intercom.<wbr>listhandlingevents</code></span></summary>
<p>Run <strong>List handling events</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listhandlingevents">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The identifier for the conversation as given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listhandlingevents">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listhitlevents">
<summary><span>List HITL events — <code>intercom.<wbr>listhitlevents</code></span></summary>
<p>Run <strong>List HITL events</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listhitlevents">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The identifier for the conversation as given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listhitlevents">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listsideconversations">
<summary><span>List side conversations — <code>intercom.<wbr>listsideconversation<wbr>s</code></span></summary>
<p>Run <strong>List side conversations</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listsideconversations">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The identifier for the conversation as given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page number of results to return (starting from 1).</td>
<td><code>default: 1</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of side conversations to return per page (max 50).</td>
<td><code>default: 25; maximum: 50</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listsideconversations">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-redactconversation">
<summary><span>Redact a conversation part — <code>intercom.<wbr>redactconversation</code></span></summary>
<p>Run <strong>Redact a conversation part</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.redactconversation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/redact_conversation_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.redactconversation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-mergeconversation">
<summary><span>Merge a conversation — <code>intercom.<wbr>mergeconversation</code></span></summary>
<p>Run <strong>Merge a conversation</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.mergeconversation">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The identifier for the secondary (source) conversation to merge away.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/merge_conversations_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.mergeconversation">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-convertconversationtoticket">
<summary><span>Convert a conversation to a ticket — <code>intercom.<wbr>convertconversationt<wbr>oticket</code></span></summary>
<p>Run <strong>Convert a conversation to a ticket</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.convertconversationtoticket">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.conversation_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The id of the conversation to target</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/convert_conversation_to_ticket_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.convertconversationtoticket">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "conversation_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listdeletedconversationids">
<summary><span>List all deleted conversation IDs — <code>intercom.<wbr>listdeletedconversat<wbr>ionids</code></span></summary>
<p>Run <strong>List all deleted conversation IDs</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listdeletedconversationids">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to first page</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>How many results per page</td>
<td><code>default: 20; maximum: 60</code></td>
</tr>
<tr>
<td><code>query.order</code></td>
<td>string</td>
<td>Optional</td>
<td><code>asc</code> or <code>desc</code>. Returns the conversation IDs in ascending or descending order. Defaults to desc</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listdeletedconversationids">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listconversationattributes">
<summary><span>List all conversation attributes — <code>intercom.<wbr>listconversationattr<wbr>ibutes</code></span></summary>
<p>Run <strong>List all conversation attributes</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listconversationattributes">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include_archived</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Include archived attributes in the list. Default <code>false</code>.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listconversationattributes">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createconversationattribute">
<summary><span>Create a conversation attribute — <code>intercom.<wbr>createconversationat<wbr>tribute</code></span></summary>
<p>Run <strong>Create a conversation attribute</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createconversationattribute">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_conversation_attribute_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createconversationattribute">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "name": "api_test_attr",
    "data_type": "string"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getconversationattribute">
<summary><span>Get a conversation attribute — <code>intercom.<wbr>getconversationattri<wbr>bute</code></span></summary>
<p>Run <strong>Get a conversation attribute</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getconversationattribute">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The conversation attribute id</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getconversationattribute">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 3
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updateconversationattribute">
<summary><span>Update a conversation attribute — <code>intercom.<wbr>updateconversationat<wbr>tribute</code></span></summary>
<p>Run <strong>Update a conversation attribute</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updateconversationattribute">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The conversation attribute id</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_conversation_attribute_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updateconversationattribute">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 8
  },
  "body": {}
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deleteconversationattribute">
<summary><span>Delete (archive) a conversation attribute — <code>intercom.<wbr>deleteconversationat<wbr>tribute</code></span></summary>
<p>Run <strong>Delete (archive) a conversation attribute</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deleteconversationattribute">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The conversation attribute id</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deleteconversationattribute">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 8
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createconversationattributeoption">
<summary><span>Add an option to a list conversation attribute — <code>intercom.<wbr>createconversationat<wbr>tributeoption</code></span></summary>
<p>Run <strong>Add an option to a list conversation attribute</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createconversationattributeoption">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The conversation attribute id</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_conversation_attribute_option_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createconversationattributeoption">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 2
  },
  "body": {
    "label": "High"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updateconversationattributeoption">
<summary><span>Update an option on a list conversation attribute — <code>intercom.<wbr>updateconversationat<wbr>tributeoption</code></span></summary>
<p>Run <strong>Update an option on a list conversation attribute</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updateconversationattributeoption">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The conversation attribute id</td>
<td></td>
</tr>
<tr>
<td><code>path.option_id</code></td>
<td>string</td>
<td>Required</td>
<td>The UUID of the list option to update (from the <code>id</code> field in the options array)</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_conversation_attribute_option_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updateconversationattributeoption">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 2,
    "option_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  },
  "body": {
    "label": "Renamed"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deleteconversationattributeoption">
<summary><span>Archive an option on a list conversation attribute — <code>intercom.<wbr>deleteconversationat<wbr>tributeoption</code></span></summary>
<p>Run <strong>Archive an option on a list conversation attribute</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deleteconversationattributeoption">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The conversation attribute id</td>
<td></td>
</tr>
<tr>
<td><code>path.option_id</code></td>
<td>string</td>
<td>Required</td>
<td>The UUID of the list option to archive (from the <code>id</code> field in the options array)</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deleteconversationattributeoption">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 2,
    "option_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createcustomobjectinstances">
<summary><span>Create or Update a Custom Object Instance — <code>intercom.<wbr>createcustomobjectin<wbr>stances</code></span></summary>
<p>Run <strong>Create or Update a Custom Object Instance</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createcustomobjectinstances">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.custom_object_type_identifier</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the custom object type that defines the structure of the custom object instance.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_or_update_custom_object_instance_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createcustomobjectinstances">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "custom_object_type_identifier": "Order"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listcustomobjectinstances">
<summary><span>List Custom Object Instances — <code>intercom.<wbr>listcustomobjectinst<wbr>ances</code></span></summary>
<p>Run <strong>List Custom Object Instances</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listcustomobjectinstances">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.custom_object_type_identifier</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the custom object type that defines the structure of the custom object instance.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.references_contact_id</code></td>
<td>string</td>
<td>Optional</td>
<td>Return instances associated with the given contact ID.</td>
<td></td>
</tr>
<tr>
<td><code>query.references_conversation_id</code></td>
<td>string</td>
<td>Optional</td>
<td>Return instances associated with the given conversation ID.</td>
<td></td>
</tr>
<tr>
<td><code>query.external_id</code></td>
<td>string</td>
<td>Optional</td>
<td>Return the single instance with this external ID. When provided, the response is a single object rather than a list.</td>
<td></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>Page number of results to fetch.</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>Number of results per page. Maximum 150.</td>
<td><code>maximum: 150</code></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listcustomobjectinstances">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "custom_object_type_identifier": "Order"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getcustomobjectinstancesbyid">
<summary><span>Get Custom Object Instance by ID — <code>intercom.<wbr>getcustomobjectinsta<wbr>ncesbyid</code></span></summary>
<p>Run <strong>Get Custom Object Instance by ID</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getcustomobjectinstancesbyid">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.custom_object_type_identifier</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the custom object type that defines the structure of the custom object instance.</td>
<td></td>
</tr>
<tr>
<td><code>path.custom_object_instance_id</code></td>
<td>string</td>
<td>Required</td>
<td>The Intercom defined id of the custom object instance. An external id here is not looked up; to find an instance by its external id, call <code>GET /custom_object_instances/{custom_object_type_identifier}?external_id=</code>.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getcustomobjectinstancesbyid">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "custom_object_type_identifier": "Order",
    "custom_object_instance_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deletecustomobjectinstancesbyid">
<summary><span>Delete a Custom Object Instance by ID — <code>intercom.<wbr>deletecustomobjectin<wbr>stancesbyid</code></span></summary>
<p>Run <strong>Delete a Custom Object Instance by ID</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deletecustomobjectinstancesbyid">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.custom_object_type_identifier</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the custom object type that defines the structure of the custom object instance.</td>
<td></td>
</tr>
<tr>
<td><code>path.custom_object_instance_id</code></td>
<td>string</td>
<td>Required</td>
<td>The Intercom defined id of the custom object instance</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deletecustomobjectinstancesbyid">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "custom_object_type_identifier": "Order",
    "custom_object_instance_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-lisdataattributes">
<summary><span>List all data attributes — <code>intercom.<wbr>lisdataattributes</code></span></summary>
<p>Run <strong>List all data attributes</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.lisdataattributes">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.model</code></td>
<td>string</td>
<td>Optional</td>
<td>Specify the data attribute model to return. For conversation attributes, use GET /conversations/attributes instead.</td>
<td><code>enum: [&quot;contact&quot;,&quot;company&quot;]</code></td>
</tr>
<tr>
<td><code>query.include_archived</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Include archived attributes in the list. By default we return only non archived data attributes.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.lisdataattributes">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createdataattribute">
<summary><span>Create a data attribute — <code>intercom.<wbr>createdataattribute</code></span></summary>
<p>Run <strong>Create a data attribute</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createdataattribute">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_data_attribute_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createdataattribute">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatedataattribute">
<summary><span>Update a data attribute — <code>intercom.<wbr>updatedataattribute</code></span></summary>
<p>Run <strong>Update a data attribute</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatedataattribute">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.data_attribute_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The data attribute id</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_data_attribute_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatedataattribute">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "data_attribute_id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listdataconnectors">
<summary><span>List all data connectors — <code>intercom.<wbr>listdataconnectors</code></span></summary>
<p>Run <strong>List all data connectors</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listdataconnectors">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results to return per page. Defaults to 20, minimum 1, maximum 50.</td>
<td><code>default: 20; minimum: 1; maximum: 50</code></td>
</tr>
<tr>
<td><code>query.starting_after</code></td>
<td>string</td>
<td>Optional</td>
<td>The cursor value from <code>pages.next.starting_after</code> in a previous response. Used to paginate through results.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listdataconnectors">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createdataconnector">
<summary><span>Create a data connector — <code>intercom.<wbr>createdataconnector</code></span></summary>
<p>Run <strong>Create a data connector</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createdataconnector">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_data_connector_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createdataconnector">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievedataconnector">
<summary><span>Retrieve a data connector — <code>intercom.<wbr>retrievedataconnecto<wbr>r</code></span></summary>
<p>Run <strong>Retrieve a data connector</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievedataconnector">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the data connector.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.state_version</code></td>
<td>string</td>
<td>Optional</td>
<td>Which version of the data connector to return. Defaults to live.</td>
<td><code>enum: [&quot;draft&quot;,&quot;live&quot;]; default: &quot;live&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievedataconnector">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "12345"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deletedataconnector">
<summary><span>Delete a data connector — <code>intercom.<wbr>deletedataconnector</code></span></summary>
<p>Run <strong>Delete a data connector</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deletedataconnector">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the data connector</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deletedataconnector">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "12345"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatedataconnector">
<summary><span>Update a data connector — <code>intercom.<wbr>updatedataconnector</code></span></summary>
<p>Run <strong>Update a data connector</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatedataconnector">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the data connector.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_data_connector_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatedataconnector">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "12345"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listdataconnectorexecutionresults">
<summary><span>List execution results for a data connector — <code>intercom.<wbr>listdataconnectorexe<wbr>cutionresults</code></span></summary>
<p>Run <strong>List execution results for a data connector</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listdataconnectorexecutionresults">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.data_connector_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the data connector.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results per page (1-30, default 10).</td>
<td><code>default: 10; minimum: 1; maximum: 30</code></td>
</tr>
<tr>
<td><code>query.starting_after</code></td>
<td>string</td>
<td>Optional</td>
<td>Cursor for pagination. Use the value from <code>pages.next.starting_after</code> in a previous response.</td>
<td></td>
</tr>
<tr>
<td><code>query.success</code></td>
<td>string</td>
<td>Optional</td>
<td>Filter by success status. Use <code>true</code>, <code>false</code>, or omit for all.</td>
<td><code>enum: [&quot;true&quot;,&quot;false&quot;]</code></td>
</tr>
<tr>
<td><code>query.error_type</code></td>
<td>string</td>
<td>Optional</td>
<td>Filter by error type.</td>
<td><code>enum: [&quot;request_configuration_error&quot;,&quot;faraday_error&quot;,&quot;3rd_party_error&quot;,&quot;response_mapping_error&quot;,&quot;token_refresh_error&quot;,&quot;fin_action_response_formatting_error&quot;,&quot;fin_action_identity_verification_error&quot;,&quot;email_verification_error&quot;,&quot;non_fin_standalone_action_identity_verification_error&quot;,&quot;request_validation_error&quot;,&quot;client_side_action_error&quot;,&quot;code_block_transformation_error&quot;,&quot;otp_preview_not_supported_error&quot;]</code></td>
</tr>
<tr>
<td><code>query.start_ts</code></td>
<td>integer</td>
<td>Optional</td>
<td>Unix timestamp for start of time range (default 1 hour ago).</td>
<td></td>
</tr>
<tr>
<td><code>query.end_ts</code></td>
<td>integer</td>
<td>Optional</td>
<td>Unix timestamp for end of time range (default now).</td>
<td></td>
</tr>
<tr>
<td><code>query.include_bodies</code></td>
<td>string</td>
<td>Optional</td>
<td>Include request/response bodies in the response (default false).</td>
<td><code>enum: [&quot;true&quot;,&quot;false&quot;]</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listdataconnectorexecutionresults">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "data_connector_id": "12345"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-showdataconnectorexecutionresult">
<summary><span>Retrieve an execution result — <code>intercom.<wbr>showdataconnectorexe<wbr>cutionresult</code></span></summary>
<p>Run <strong>Retrieve an execution result</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.showdataconnectorexecutionresult">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.data_connector_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the data connector.</td>
<td></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the execution result.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.showdataconnectorexecutionresult">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "data_connector_id": "12345",
    "id": "99001"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listdataconnectorversions">
<summary><span>List versions of a data connector — <code>intercom.<wbr>listdataconnectorver<wbr>sions</code></span></summary>
<p>Run <strong>List versions of a data connector</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listdataconnectorversions">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the data connector.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of results per page (1-50, default 20). Values outside this range are clamped, so values below 1 are treated as 1. A non-integer value falls back to the default of 20.</td>
<td><code>default: 20; minimum: 1; maximum: 50</code></td>
</tr>
<tr>
<td><code>query.starting_after</code></td>
<td>string</td>
<td>Optional</td>
<td>Cursor for pagination. Use the value from <code>pages.next.starting_after</code> in a previous response.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listdataconnectorversions">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "12345"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievedataconnectorversion">
<summary><span>Retrieve a version of a data connector — <code>intercom.<wbr>retrievedataconnecto<wbr>rversion</code></span></summary>
<p>Run <strong>Retrieve a version of a data connector</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievedataconnectorversion">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the data connector.</td>
<td></td>
</tr>
<tr>
<td><code>path.version_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The <code>entity_version_id</code> of the version, as returned by <a href="https://developers.intercom.com/docs/references/rest-api/api.intercom.io/data-connectors/listdataconnectorversions">List versions of a data connector</a>.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievedataconnectorversion">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "12345",
    "version_id": 9821
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatedataconnectorversion">
<summary><span>Update the note on a data connector version — <code>intercom.<wbr>updatedataconnectorv<wbr>ersion</code></span></summary>
<p>Run <strong>Update the note on a data connector version</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatedataconnectorversion">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the data connector.</td>
<td></td>
</tr>
<tr>
<td><code>path.version_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The <code>entity_version_id</code> of the version, as returned by <a href="https://developers.intercom.com/docs/references/rest-api/api.intercom.io/data-connectors/listdataconnectorversions">List versions of a data connector</a>.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Required</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_data_connector_version_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatedataconnectorversion">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "12345",
    "version_id": 9821
  },
  "body": {
    "note": "Switched to the v2 orders endpoint"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createdataevent">
<summary><span>Submit a data event — <code>intercom.<wbr>createdataevent</code></span></summary>
<p>Run <strong>Submit a data event</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createdataevent">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_data_event_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createdataevent">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-lisdataevents">
<summary><span>List all data events — <code>intercom.<wbr>lisdataevents</code></span></summary>
<p>Run <strong>List all data events</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.lisdataevents">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.filter</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.filter</code></td>
<td>object</td>
<td>Required</td>
<td>user_id query parameter</td>
<td><code>oneOf[1]; additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.filter.user_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>oneOf[1]</code></td>
</tr>
<tr>
<td><code>query.filter</code></td>
<td>object</td>
<td>Required</td>
<td>intercom_user_id query parameter</td>
<td><code>oneOf[2]; additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.filter.intercom_user_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>oneOf[2]</code></td>
</tr>
<tr>
<td><code>query.filter</code></td>
<td>object</td>
<td>Required</td>
<td>email query parameter</td>
<td><code>oneOf[3]; additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.filter.email</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>oneOf[3]</code></td>
</tr>
<tr>
<td><code>query.filter</code></td>
<td>object</td>
<td>Required</td>
<td>anonymous_id query parameter</td>
<td><code>oneOf[4]; additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.filter.anonymous_id</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>oneOf[4]</code></td>
</tr>
<tr>
<td><code>query.type</code></td>
<td>string</td>
<td>Required</td>
<td>The value must be <code>user</code> or <code>lead</code>.</td>
<td><code>enum: [&quot;user&quot;,&quot;lead&quot;]</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of events to return per page.</td>
<td></td>
</tr>
<tr>
<td><code>query.since</code></td>
<td>integer</td>
<td>Optional</td>
<td>Only return events created after this time, as a Unix timestamp in milliseconds. Take the value from the <code>since</code> link in the <code>pages</code> object of a previous response.</td>
<td></td>
</tr>
<tr>
<td><code>query.before</code></td>
<td>integer</td>
<td>Optional</td>
<td>Only return events created before this time, as a Unix timestamp in milliseconds. Take the value from the <code>next</code> link in the <code>pages</code> object of a previous response.</td>
<td></td>
</tr>
<tr>
<td><code>query.summary</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Set to <code>true</code> (or <code>1</code>) to return an event summary (<code>event.summary</code>) instead of the list of events. Omit for the paginated event list (<code>event.list</code>).</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.lisdataevents">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "filter": {
      "user_id": "example"
    },
    "type": "user"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-dataeventsummaries">
<summary><span>Create event summaries — <code>intercom.<wbr>dataeventsummaries</code></span></summary>
<p>Run <strong>Create event summaries</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.dataeventsummaries">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_data_event_summaries_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.dataeventsummaries">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createdataexport">
<summary><span>Create content data export — <code>intercom.<wbr>createdataexport</code></span></summary>
<p>Run <strong>Create content data export</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createdataexport">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_data_exports_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createdataexport">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getdataexport">
<summary><span>Show content data export — <code>intercom.<wbr>getdataexport</code></span></summary>
<p>Run <strong>Show content data export</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getdataexport">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.job_identifier</code></td>
<td>string</td>
<td>Required</td>
<td>job_identifier</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getdataexport">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "job_identifier": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-canceldataexport">
<summary><span>Cancel content data export — <code>intercom.<wbr>canceldataexport</code></span></summary>
<p>Run <strong>Cancel content data export</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.canceldataexport">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.job_identifier</code></td>
<td>string</td>
<td>Required</td>
<td>job_identifier</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.canceldataexport">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "job_identifier": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-downloaddataexport">
<summary><span>Download content data export — <code>intercom.<wbr>downloaddataexport</code></span></summary>
<p>Run <strong>Download content data export</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.downloaddataexport">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.job_identifier</code></td>
<td>string</td>
<td>Required</td>
<td>job_identifier</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.downloaddataexport">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "job_identifier": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-jobsstatus">
<summary><span>Retrieve job status — <code>intercom.<wbr>jobsstatus</code></span></summary>
<p>Run <strong>Retrieve job status</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.jobsstatus">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.job_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the job which is given by Intercom</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.jobsstatus">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "job_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createmessage">
<summary><span>Create a message — <code>intercom.<wbr>createmessage</code></span></summary>
<p>Run <strong>Create a message</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createmessage">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_message_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createmessage">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievewhatsappmessagestatus">
<summary><span>Retrieve WhatsApp message delivery status — <code>intercom.<wbr>retrievewhatsappmess<wbr>agestatus</code></span></summary>
<p>Run <strong>Retrieve WhatsApp message delivery status</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievewhatsappmessagestatus">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.message_id</code></td>
<td>string</td>
<td>Required</td>
<td>The WhatsApp message ID to check status for</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievewhatsappmessagestatus">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "message_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getwhatsappmessagestatus">
<summary><span>Get statuses of all messages sent based on the specified ruleset_id — <code>intercom.<wbr>getwhatsappmessagest<wbr>atus</code></span></summary>
<p>Run <strong>Get statuses of all messages sent based on the specified ruleset_id</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getwhatsappmessagestatus">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.ruleset_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the set of messages to check status for</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>Number of results per page (default 50, max 100)</td>
<td><code>default: 50; maximum: 100</code></td>
</tr>
<tr>
<td><code>query.starting_after</code></td>
<td>string</td>
<td>Optional</td>
<td>Cursor for pagination, used to fetch the next page of results</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getwhatsappmessagestatus">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "ruleset_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listnewsitems">
<summary><span>List all news items — <code>intercom.<wbr>listnewsitems</code></span></summary>
<p>Run <strong>List all news items</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listnewsitems">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch.</td>
<td><code>default: 1</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of news items to return per page. Values above 20 are reduced to 20.</td>
<td><code>default: 10; maximum: 20</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listnewsitems">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createnewsitem">
<summary><span>Create a news item — <code>intercom.<wbr>createnewsitem</code></span></summary>
<p>Run <strong>Create a news item</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createnewsitem">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/news_item_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createnewsitem">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievenewsitem">
<summary><span>Retrieve a news item — <code>intercom.<wbr>retrievenewsitem</code></span></summary>
<p>Run <strong>Retrieve a news item</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievenewsitem">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.news_item_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the news item which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievenewsitem">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "news_item_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatenewsitem">
<summary><span>Update a news item — <code>intercom.<wbr>updatenewsitem</code></span></summary>
<p>Run <strong>Update a news item</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatenewsitem">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.news_item_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the news item which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_news_item_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatenewsitem">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "news_item_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deletenewsitem">
<summary><span>Delete a news item — <code>intercom.<wbr>deletenewsitem</code></span></summary>
<p>Run <strong>Delete a news item</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deletenewsitem">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.news_item_id</code></td>
<td>integer</td>
<td>Required</td>
<td>The unique identifier for the news item which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deletenewsitem">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "news_item_id": 123
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listlivenewsfeeditems">
<summary><span>List all live newsfeed items — <code>intercom.<wbr>listlivenewsfeeditem<wbr>s</code></span></summary>
<p>Run <strong>List all live newsfeed items</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listlivenewsfeeditems">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.newsfeed_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the news feed item which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch.</td>
<td><code>default: 1</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of news items to return per page. Values above 20 are reduced to 20.</td>
<td><code>default: 20; maximum: 20</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listlivenewsfeeditems">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "newsfeed_id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listnewsfeeds">
<summary><span>List all newsfeeds — <code>intercom.<wbr>listnewsfeeds</code></span></summary>
<p>Run <strong>List all newsfeeds</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listnewsfeeds">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch.</td>
<td><code>default: 1</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of newsfeeds to return per page. Values above 20 are reduced to 20.</td>
<td><code>default: 10; maximum: 20</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listnewsfeeds">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievenewsfeed">
<summary><span>Retrieve a newsfeed — <code>intercom.<wbr>retrievenewsfeed</code></span></summary>
<p>Run <strong>Retrieve a newsfeed</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievenewsfeed">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.newsfeed_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the news feed item which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievenewsfeed">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "newsfeed_id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievenote">
<summary><span>Retrieve a note — <code>intercom.<wbr>retrievenote</code></span></summary>
<p>Run <strong>Retrieve a note</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievenote">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.note_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of a given note</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievenote">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "note_id": "34"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deletenote">
<summary><span>Delete a note — <code>intercom.<wbr>deletenote</code></span></summary>
<p>Run <strong>Delete a note</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deletenote">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.note_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of a given note</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deletenote">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "note_id": "34"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listsegments">
<summary><span>List all segments — <code>intercom.<wbr>listsegments</code></span></summary>
<p>Run <strong>List all segments</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listsegments">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include_count</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Includes the count of contacts that belong to each segment. The counts are added whenever this parameter has a value in the query string, even <code>false</code> or an empty one, so omit it entirely to leave them out. A bare <code>include_count</code> with no <code>=</code> adds no counts. With <code>type=company</code>, a company segment gets no count unless a contact segment has the same name, and then it shows that contact segment&#39;s count.</td>
<td></td>
</tr>
<tr>
<td><code>query.type</code></td>
<td>string</td>
<td>Optional</td>
<td>Pass <code>company</code> to list company segments. Any other value, or no value, lists contact segments.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listsegments">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievesegment">
<summary><span>Retrieve a segment — <code>intercom.<wbr>retrievesegment</code></span></summary>
<p>Run <strong>Retrieve a segment</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievesegment">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.segment_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identified of a given segment.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.include_count</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Includes the count of contacts that belong to the segment. The count is added whenever this parameter has a value in the query string, even <code>false</code> or an empty one, so omit it entirely to leave it out. A bare <code>include_count</code> with no <code>=</code> adds no count.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievesegment">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "segment_id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listsubscriptiontypes">
<summary><span>List subscription types — <code>intercom.<wbr>listsubscriptiontype<wbr>s</code></span></summary>
<p>Run <strong>List subscription types</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listsubscriptiontypes">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listsubscriptiontypes">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getsubscriptiontype">
<summary><span>Retrieve a subscription type — <code>intercom.<wbr>getsubscriptiontype</code></span></summary>
<p>Run <strong>Retrieve a subscription type</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getsubscriptiontype">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the subscription type.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getsubscriptiontype">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createphoneswitch">
<summary><span>Create a phone Switch — <code>intercom.<wbr>createphoneswitch</code></span></summary>
<p>Run <strong>Create a phone Switch</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createphoneswitch">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_phone_switch_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createphoneswitch">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listcalls">
<summary><span>List all calls — <code>intercom.<wbr>listcalls</code></span></summary>
<p>Run <strong>List all calls</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listcalls">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td>The page of results to fetch. Defaults to first page</td>
<td></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td>How many results to display per page. Defaults to 25. Must be between 1 and 25. A value outside that range returns a 400 error.</td>
<td><code>minimum: 1; maximum: 25</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listcalls">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-showcall">
<summary><span>Get a call — <code>intercom.<wbr>showcall</code></span></summary>
<p>Run <strong>Get a call</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.showcall">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.call_id</code></td>
<td>string</td>
<td>Required</td>
<td>The id of the call to retrieve</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.showcall">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "call_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-showcalltranscript">
<summary><span>Get call transcript by call id — <code>intercom.<wbr>showcalltranscript</code></span></summary>
<p>Run <strong>Get call transcript by call id</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.showcalltranscript">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The id of the call</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.showcalltranscript">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listcallswithtranscripts">
<summary><span>List calls with transcripts — <code>intercom.<wbr>listcallswithtranscr<wbr>ipts</code></span></summary>
<p>Run <strong>List calls with transcripts</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listcallswithtranscripts">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.conversation_ids</code></td>
<td>array</td>
<td>Required</td>
<td>A list of conversation ids to fetch calls for. Maximum 20.</td>
<td><code>minItems: 1; maxItems: 20</code></td>
</tr>
<tr>
<td><code>body.conversation_ids[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listcallswithtranscripts">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "conversation_ids": [
      "64619700005694",
      "64619700005695"
    ]
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listtags">
<summary><span>List all tags — <code>intercom.<wbr>listtags</code></span></summary>
<p>Run <strong>List all tags</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listtags">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.id</code></td>
<td>string</td>
<td>Optional</td>
<td>The unique identifier of a tag. When set, a single tag object is returned instead of a list.</td>
<td></td>
</tr>
<tr>
<td><code>query.taggable_type</code></td>
<td>string</td>
<td>Optional</td>
<td>Set to <code>user</code> or <code>company</code> to list the tags applied to one contact or company instead of the whole workspace. Identify it with <code>taggable_id</code>, <code>user_id</code>, <code>email</code>, <code>company_id</code> or <code>name</code>.</td>
<td><code>enum: [&quot;user&quot;,&quot;company&quot;]</code></td>
</tr>
<tr>
<td><code>query.taggable_id</code></td>
<td>string</td>
<td>Optional</td>
<td>The Intercom id of the contact or company whose tags you want, used with <code>taggable_type</code>.</td>
<td></td>
</tr>
<tr>
<td><code>query.user_id</code></td>
<td>string</td>
<td>Optional</td>
<td>The external id of the contact whose tags you want, used with <code>taggable_type=user</code>.</td>
<td></td>
</tr>
<tr>
<td><code>query.email</code></td>
<td>string</td>
<td>Optional</td>
<td>The email address of the contact whose tags you want, used with <code>taggable_type=user</code>.</td>
<td></td>
</tr>
<tr>
<td><code>query.company_id</code></td>
<td>string</td>
<td>Optional</td>
<td>The external id of the company whose tags you want, used with <code>taggable_type=company</code>.</td>
<td></td>
</tr>
<tr>
<td><code>query.name</code></td>
<td>string</td>
<td>Optional</td>
<td>The name of the company whose tags you want, used with <code>taggable_type=company</code>.</td>
<td></td>
</tr>
<tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listtags">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createtag">
<summary><span>Create or update a tag, Tag or untag companies, Tag contacts — <code>intercom.<wbr>createtag</code></span></summary>
<p>Run <strong>Create or update a tag, Tag or untag companies, Tag contacts</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createtag">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>anyOf[1]; $ref: &quot;#/definitions/create_or_update_tag_request&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>anyOf[2]; $ref: &quot;#/definitions/tag_company_request&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>anyOf[3]; $ref: &quot;#/definitions/untag_company_request&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>anyOf[4]; $ref: &quot;#/definitions/tag_multiple_users_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createtag">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-findtag">
<summary><span>Find a specific tag — <code>intercom.<wbr>findtag</code></span></summary>
<p>Run <strong>Find a specific tag</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.findtag">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.tag_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of a given tag</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.findtag">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "tag_id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deletetag">
<summary><span>Delete tag — <code>intercom.<wbr>deletetag</code></span></summary>
<p>Run <strong>Delete tag</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deletetag">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.tag_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of a given tag</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deletetag">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "tag_id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listteams">
<summary><span>List all teams — <code>intercom.<wbr>listteams</code></span></summary>
<p>Run <strong>List all teams</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listteams">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listteams">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrieveteam">
<summary><span>Retrieve a team — <code>intercom.<wbr>retrieveteam</code></span></summary>
<p>Run <strong>Retrieve a team</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrieveteam">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.team_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of a given team.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrieveteam">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "team_id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getteammetrics">
<summary><span>Retrieve team metrics — <code>intercom.<wbr>getteammetrics</code></span></summary>
<p>Run <strong>Retrieve team metrics</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getteammetrics">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.team_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the team to retrieve metrics for. Use <code>GET /teams</code> to list available team IDs.</td>
<td></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.idle_threshold</code></td>
<td>integer</td>
<td>Optional</td>
<td>The number of seconds after which an open conversation is considered idle. Clamped to the range 1–86400. Defaults to 1800 (30 minutes).</td>
<td><code>default: 1800</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getteammetrics">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "team_id": "42"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listticketstates">
<summary><span>List all ticket states — <code>intercom.<wbr>listticketstates</code></span></summary>
<p>Run <strong>List all ticket states</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listticketstates">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listticketstates">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createtickettypeattribute">
<summary><span>Create a new attribute for a ticket type — <code>intercom.<wbr>createtickettypeattr<wbr>ibute</code></span></summary>
<p>Run <strong>Create a new attribute for a ticket type</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createtickettypeattribute">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ticket_type_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the ticket type which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_ticket_type_attribute_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createtickettypeattribute">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ticket_type_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatetickettypeattribute">
<summary><span>Update an existing attribute for a ticket type — <code>intercom.<wbr>updatetickettypeattr<wbr>ibute</code></span></summary>
<p>Run <strong>Update an existing attribute for a ticket type</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatetickettypeattribute">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ticket_type_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the ticket type which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>path.attribute_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the ticket type attribute which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_ticket_type_attribute_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatetickettypeattribute">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ticket_type_id": "example",
    "attribute_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listtickettypes">
<summary><span>List all ticket types — <code>intercom.<wbr>listtickettypes</code></span></summary>
<p>Run <strong>List all ticket types</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listtickettypes">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listtickettypes">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createtickettype">
<summary><span>Create a ticket type — <code>intercom.<wbr>createtickettype</code></span></summary>
<p>Run <strong>Create a ticket type</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createtickettype">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/create_ticket_type_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createtickettype">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-gettickettype">
<summary><span>Retrieve a ticket type — <code>intercom.<wbr>gettickettype</code></span></summary>
<p>Run <strong>Retrieve a ticket type</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.gettickettype">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ticket_type_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the ticket type which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.gettickettype">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ticket_type_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatetickettype">
<summary><span>Update a ticket type — <code>intercom.<wbr>updatetickettype</code></span></summary>
<p>Run <strong>Update a ticket type</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatetickettype">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ticket_type_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the ticket type which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_ticket_type_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatetickettype">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ticket_type_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-replyticket">
<summary><span>Reply to a ticket — <code>intercom.<wbr>replyticket</code></span></summary>
<p>Run <strong>Reply to a ticket</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.replyticket">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ticket_id</code></td>
<td>string</td>
<td>Required</td>
<td>The id of the ticket to target. {% admonition type=&quot;info&quot; name=&quot;Not the Inbox ticket ID&quot; %} This is the internal <code>id</code> field from the API response, not the <code>ticket_id</code> displayed in the Intercom Inbox (e.g., #12345). Use the <code>id</code> value from the ticket object returned by the API. {% /admonition %}</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.skip_notifications</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Option to disable notifications when replying to a Ticket.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>oneOf[1]; $ref: &quot;#/definitions/contact_reply_ticket_request&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>oneOf[2]; $ref: &quot;#/definitions/admin_reply_ticket_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.replyticket">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ticket_id": "123"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-attachtagtoticket">
<summary><span>Add tag to a ticket — <code>intercom.<wbr>attachtagtoticket</code></span></summary>
<p>Run <strong>Add tag to a ticket</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.attachtagtoticket">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ticket_id</code></td>
<td>string</td>
<td>Required</td>
<td>ticket_id</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the tag which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>body.admin_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the admin which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.attachtagtoticket">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ticket_id": "64619700005694"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-detachtagfromticket">
<summary><span>Remove tag from a ticket — <code>intercom.<wbr>detachtagfromticket</code></span></summary>
<p>Run <strong>Remove tag from a ticket</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.detachtagfromticket">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ticket_id</code></td>
<td>string</td>
<td>Required</td>
<td>ticket_id</td>
<td></td>
</tr>
<tr>
<td><code>path.tag_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the tag which is given by Intercom</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.admin_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the admin which is given by Intercom.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.detachtagfromticket">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ticket_id": "64619700005694",
    "tag_id": "7522907"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-linkconversationtoticket">
<summary><span>Link a conversation to a ticket — <code>intercom.<wbr>linkconversationtoti<wbr>cket</code></span></summary>
<p>Run <strong>Link a conversation to a ticket</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.linkconversationtoticket">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ticket_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the tracker ticket which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.conversation_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier (given by Intercom) for the conversation or customer ticket to link to the tracker ticket.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.linkconversationtoticket">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ticket_id": "64619700005694"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-unlinkconversationfromticket">
<summary><span>Unlink a conversation from a ticket — <code>intercom.<wbr>unlinkconversationfr<wbr>omticket</code></span></summary>
<p>Run <strong>Unlink a conversation from a ticket</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.unlinkconversationfromticket">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ticket_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the tracker ticket which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier (given by Intercom) for the linked conversation or customer ticket to unlink.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.unlinkconversationfromticket">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ticket_id": "64619700005694",
    "id": "204"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-createticket">
<summary><span>Create a ticket — <code>intercom.<wbr>createticket</code></span></summary>
<p>Run <strong>Create a ticket</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.createticket">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.skip_notifications</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Option to disable notifications when a Ticket is created.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/create_ticket_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.createticket">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-enqueuecreateticket">
<summary><span>Enqueue create ticket — <code>intercom.<wbr>enqueuecreateticket</code></span></summary>
<p>Run <strong>Enqueue create ticket</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.enqueuecreateticket">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.skip_notifications</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Option to disable notifications when a Ticket is created.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/create_ticket_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.enqueuecreateticket">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updateticket">
<summary><span>Update a ticket — <code>intercom.<wbr>updateticket</code></span></summary>
<p>Run <strong>Update a ticket</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updateticket">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ticket_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the ticket which is given by Intercom. {% admonition type=&quot;info&quot; name=&quot;Not the Inbox ticket ID&quot; %} This is the internal <code>id</code> field from the API response, not the <code>ticket_id</code> displayed in the Intercom Inbox (e.g., #12345). Use the <code>id</code> value from the ticket object returned by the API. {% /admonition %}</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.skip_notifications</code></td>
<td>boolean</td>
<td>Optional</td>
<td>Option to disable notifications when a Ticket is updated.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>allOf[1]; $ref: &quot;#/definitions/update_ticket_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updateticket">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ticket_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-getticket">
<summary><span>Retrieve a ticket — <code>intercom.<wbr>getticket</code></span></summary>
<p>Run <strong>Retrieve a ticket</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.getticket">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ticket_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the ticket which is given by Intercom. {% admonition type=&quot;info&quot; name=&quot;Not the Inbox ticket ID&quot; %} This is the internal <code>id</code> field from the API response, not the <code>ticket_id</code> displayed in the Intercom Inbox (e.g., #12345). Use the <code>id</code> value from the ticket object returned by the API. {% /admonition %}</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.getticket">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ticket_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-deleteticket">
<summary><span>Delete a ticket — <code>intercom.<wbr>deleteticket</code></span></summary>
<p>Run <strong>Delete a ticket</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.deleteticket">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ticket_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the ticket which is given by Intercom. {% admonition type=&quot;info&quot; name=&quot;Not the Inbox ticket ID&quot; %} This is the internal <code>id</code> field from the API response, not the <code>ticket_id</code> displayed in the Intercom Inbox (e.g., #12345). Use the <code>id</code> value from the ticket object returned by the API. {% /admonition %}</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.deleteticket">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ticket_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-changetickettype">
<summary><span>Change ticket type — <code>intercom.<wbr>changetickettype</code></span></summary>
<p>Run <strong>Change ticket type</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.changetickettype">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.ticket_id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier for the ticket which is given by Intercom.</td>
<td></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/change_ticket_type_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.changetickettype">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "ticket_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-searchtickets">
<summary><span>Search tickets — <code>intercom.<wbr>searchtickets</code></span></summary>
<p>Run <strong>Search tickets</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.searchtickets">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/search_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.searchtickets">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-updatevisitor">
<summary><span>Update a visitor — <code>intercom.<wbr>updatevisitor</code></span></summary>
<p>Run <strong>Update a visitor</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.updatevisitor">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/update_visitor_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.updatevisitor">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievevisitorwithuserid">
<summary><span>Retrieve a visitor with User ID — <code>intercom.<wbr>retrievevisitorwithu<wbr>serid</code></span></summary>
<p>Run <strong>Retrieve a visitor with User ID</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievevisitorwithuserid">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>query</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.user_id</code></td>
<td>string</td>
<td>Required</td>
<td>The user_id of the Visitor you want to retrieve.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievevisitorwithuserid">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "query": {
    "user_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-convertvisitor">
<summary><span>Convert a visitor — <code>intercom.<wbr>convertvisitor</code></span></summary>
<p>Run <strong>Convert a visitor</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.convertvisitor">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/convert_visitor_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.convertvisitor">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listbrands">
<summary><span>List all brands — <code>intercom.<wbr>listbrands</code></span></summary>
<p>Run <strong>List all brands</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listbrands">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listbrands">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrievebrand">
<summary><span>Retrieve a brand — <code>intercom.<wbr>retrievebrand</code></span></summary>
<p>Run <strong>Retrieve a brand</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrievebrand">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the brand</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrievebrand">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-listemails">
<summary><span>List all email settings — <code>intercom.<wbr>listemails</code></span></summary>
<p>Run <strong>List all email settings</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.listemails">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.listemails">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-retrieveemail">
<summary><span>Retrieve an email setting — <code>intercom.<wbr>retrieveemail</code></span></summary>
<p>Run <strong>Retrieve an email setting</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.retrieveemail">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The unique identifier of the email setting</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.retrieveemail">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-registerfinvoicecall">
<summary><span>Register a Fin Voice call — <code>intercom.<wbr>registerfinvoicecall</code></span></summary>
<p>Run <strong>Register a Fin Voice call</strong> with Intercom. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.registerfinvoicecall">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>$ref: &quot;#/definitions/register_fin_voice_call_request&quot;</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.registerfinvoicecall">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-collectfinvoicecallbyid">
<summary><span>Collect Fin Voice call by ID — <code>intercom.<wbr>collectfinvoicecallb<wbr>yid</code></span></summary>
<p>Run <strong>Collect Fin Voice call by ID</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.collectfinvoicecallbyid">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>integer</td>
<td>Required</td>
<td>The external reference ID</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.collectfinvoicecallbyid">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-collectfinvoicecallbyexternalid">
<summary><span>Collect Fin Voice call by external ID — <code>intercom.<wbr>collectfinvoicecallb<wbr>yexternalid</code></span></summary>
<p>Run <strong>Collect Fin Voice call by external ID</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.collectfinvoicecallbyexternalid">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.external_id</code></td>
<td>string</td>
<td>Required</td>
<td>The external call identifier from the call provider</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.collectfinvoicecallbyexternalid">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "external_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-collectfinvoicecallbyphonenumber">
<summary><span>Collect Fin Voice call by phone number — <code>intercom.<wbr>collectfinvoicecallb<wbr>yphonenumber</code></span></summary>
<p>Run <strong>Collect Fin Voice call by phone number</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.collectfinvoicecallbyphonenumber">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.phone_number</code></td>
<td>string</td>
<td>Required</td>
<td>Phone number in E.164 format</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.collectfinvoicecallbyphonenumber">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "phone_number": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-collectfinvoicecallsbyconversationid">
<summary><span>Collect Fin Voice calls by conversation ID — <code>intercom.<wbr>collectfinvoicecalls<wbr>byconversationid</code></span></summary>
<p>Run <strong>Collect Fin Voice calls by conversation ID</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.collectfinvoicecallsbyconversationid">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.conversation_id</code></td>
<td>string</td>
<td>Required</td>
<td>The Intercom conversation identifier</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.collectfinvoicecallsbyconversationid">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "conversation_id": "example"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-intercom-exportworkflow">
<summary><span>Export a workflow — <code>intercom.<wbr>exportworkflow</code></span></summary>
<p>Run <strong>Export a workflow</strong> with Intercom. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/intercom?command=intercom.exportworkflow">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>headers</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>headers.Intercom-Version</code></td>
<td>—</td>
<td>Optional</td>
<td></td>
<td><code>enum: [&quot;2.17&quot;]; $ref: &quot;#/definitions/intercom_version&quot;</code></td>
</tr>
<tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.id</code></td>
<td>string</td>
<td>Required</td>
<td>The ruleset ID of the workflow. This is the number at the end of the workflow&#39;s URL in Intercom, <code>https://app.intercom.com/a/apps/&amp;lt;app_id&amp;gt;/automation/workflows/&amp;lt;id&amp;gt;</code>. It is not the <code>workflow.id</code> returned in the response, so don&#39;t pass that value back here.</td>
<td></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/intercom/commands/intercom.exportworkflow">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "id": "12345"
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://developers.intercom.com/docs/references/rest-api/api.intercom.io/2.17">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/intercom/index.mdx
