Intercom: List Content Import Sources

List content import sources.

Tool ID: intercom_list_content_import_sources

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'intercom_list_content_import_sources',
  {},
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute intercom_list_content_import_sources --input '{}' --json

Example response

The static output schema is not detailed enough to generate a reliable example. Use deepline tools get intercom_list_content_import_sources --json for the complete live contract.

Input reference

You can retrieve a list of all content import sources for a workspace. This action does not require input fields.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	This will return a list of the content import sources for the App.
`result.data.type`	`"list"`	No	—	The type of the object - `list`. Allowed: `list`.
`result.data.pages`	`object`	No	—	The majority of list resources in the API are paginated to allow clients to traverse data over multiple requests. Their responses are likely to contain a pages object that hosts pagination links which a client can use to paginate through the data without having to construct a query. The link relations for the pages field are as follows.
`result.data.pages.type`	`"pages"`	No	—	Allowed: `pages`.
`result.data.pages.page`	`integer`	No	—	—
`result.data.pages.next`	`string \| null`	No	—	A link to the next page of results. A response that does not contain a next link does not have further data to fetch. Format: `uri`.
`result.data.pages.per_page`	`integer`	No	—	—
`result.data.pages.total_pages`	`integer`	No	—	—
`result.data.total_count`	`integer`	No	—	A count of the total number of content import sources.
`result.data.data`	`array`	No	—	An array of Content Import Source objects
`result.data.data[].type`	`"content_import_source"`	Yes	`"content_import_source"`	Always external_page Allowed: `content_import_source`.
`result.data.data[].id`	`integer`	Yes	—	The unique identifier for the content import source which is given by Intercom.
`result.data.data[].last_synced_at`	`integer`	Yes	—	The time when the content import source was last synced. Format: `date-time`.
`result.data.data[].sync_behavior`	`"api" \| "automatic" \| "manual"`	Yes	—	If you intend to create or update External Pages via the API, this should be set to `api`. Allowed: `api`, `automatic`, `manual`.
`result.data.data[].status`	`"active" \| "deactivated"`	Yes	`"active"`	The status of the content import source. Allowed: `active`, `deactivated`.
`result.data.data[].url`	`string`	Yes	—	The URL of the root of the external source.
`result.data.data[].created_at`	`integer`	Yes	—	The time when the content import source was created. Format: `date-time`.
`result.data.data[].updated_at`	`integer`	Yes	—	The time when the content import source was last updated. Format: `date-time`.
`result.data.data[].audience_ids`	`array \| null`	No	—	The unique identifiers for the audiences associated with this content import source.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Intercom: List Content Import Sources

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation