MULTI-APP TOOLKIT
Build with Intercom + Jira
- Multi-app
- One MCP session
- 52 actions
- 20 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Intercom and Jira tool at once — connect once, list tools, and call them like any single-app session.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "intercom,jira",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Intercom and Jira tools arrive
// together, each keyed by its own app's slug.
// e.g. run Add Tag To Contact:
const result = await mcp.callTool({
name: "intercom-add-tag-to-contact",
arguments: {
contactId: "Contact ID",
tagId: "Tag ID",
},
})import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const externalUserId = "{external_user_id}" // any stable ID for this user in your system
const [intercomTools, jiraTools] =
await Promise.all([
pd.components.list({ app: "intercom" }),
pd.components.list({ app: "jira" }),
])
// One external user owns both connected accounts, so either app's tools
// run on their behalf with the same externalUserId.curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=intercom" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=jira" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
# Connect both accounts to the same external_user_id, then
# configure and invoke either app's tools on that user's behalf.ARCHITECTURE
One user, two connected accounts
Your user connects each account once, under whatever ID they already have in your product. The two stay independent — either can be revoked on its own — and your code reaches both through that one user.
Your product
external_user_id
{external_user_id}Pipedream Connect
Managed identity
Auth · tools · routing
Intercom
Connected account
Jira
Connected account
TOOLS
Intercom tools
The Intercom tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 13
-
Add Tag To Contact
actionAdds a specific tag to a contact in Intercom. Use Search Contacts to find the contact's ID and List Tag ID Options to find valid tag IDs before calling this action. Example: set Contact ID to63a07ddf05a32042dffac965and Tag ID to7522907to tag that contact. Returns the updated tag object on success. See the documentation.Writev0.0.5 -
Create Note
actionCreates a note on a contact's record in Intercom. The note is automatically attributed to the currently authenticated admin — no Admin ID prop is required. Use Search Contacts to find the contact's ID before calling this action. Example: set User to63a07ddf05a32042dffac965and Body toFollowed up via email on 2024-01-15to log a note on that contact. Returns the new note object includingid,body, andauthor. See the documentationWritev0.0.9 -
List Admin ID Options
actionRetrieves all admins in your Intercom workspace and returns their IDs and names. Call this action before any action that requires an Admin ID — such as Manage A Conversation, Reply To Conversation, or Send Message To Contact — to discover valid values. Example: returns[{ label: "Jane Doe", value: "25" }, ...]. See the documentation.Read-onlyv0.0.3 -
List Assignee ID Options
actionRetrieves all teams in your Intercom workspace and returns their IDs and names. Call this action before Manage A Conversation to discover valid team IDs for conversation assignment. Example: returns[{ label: "Support", value: "334" }, ...]. Use0to represent Unassigned. See the documentation.Read-onlyv0.0.3 -
List Conversations
actionLists conversations in your Intercom workspace, most recently updated first (GET /conversations). Use this to discover a conversation's ID before calling Reply To Conversation, Manage A Conversation, or Retrieve Conversation — there is no other way to look one up. Returns a bounded page of conversations, each includingid,state,created_at, and the latest message part. Ifpages.next.starting_afteris present in the response, call this action again with that cursor in Starting After to retrieve the next page. Pass Fields (e.g.["id", "state", "created_at"]) to limit each returned conversation to only those keys. Example: leave all props empty to fetch the 20 most recently updated conversations. See the documentation.Read-onlyv0.0.2 -
List Tag ID Options
actionRetrieves all tags in your Intercom workspace and returns their IDs and names. Call this action before Add Tag To Contact to discover valid tag IDs. Example: returns[{ label: "VIP", value: "7522907" }, ...]. See the documentation.Read-onlyv0.0.3 -
Manage A Conversation
actionClose, snooze, open, or assign a conversation by its ID. Which of the optional props apply depends on Message Type:closeuses Body,snoozeduses Snoozed Until,assignmentuses Type together with Assignee ID or Team Assignee ID, andopenuses none of them. Example: set Conversation ID to192783634529321, Message Type toclose, and Body toIssue resolvedto close that conversation with a closing comment. See the documentation.Writev0.1.2 -
Reply To Conversation
actionReply to an existing Intercom conversation as an admin or on behalf of a contact (POST /conversations/{conversation_id}/reply). Use List Admin ID Options to find a valid Admin ID, and Search Contacts to find a contact's Intercom user ID, email, or external user ID. Example: set Conversation ID to192783634529321, Reply Type toadmin, Message Type tocomment, Body toThanks for reaching out!, and Admin ID to25to post that comment as an admin reply. See the documentation.Writev0.1.1
Triggers top 4 of 16
-
New Companies
triggerEmit new event each time a new company is added.v0.0.9 -
New Reply From Admin
triggerEmit new event each time an admin replies to a conversation.v0.0.9 -
New Conversations
triggerEmit new event each time a new conversation is added.v0.0.9 -
New Reply From User
triggerEmit new event each time a user replies to a conversation.v0.0.9
TOOLS
Jira tools
The Jira tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 39
-
Add Attachment To Issue
actionAdds an attachment to an issue. See the documentationWritev1.0.18 -
Add Comment To Issue
actionAdds a new comment to an issue. See the documentationWritev0.1.25 -
Add Multiple Attachments To Issue
actionAdds multiple attachments to an issue. See the documentationWritev1.0.18 -
Add Watcher To Issue
actionAdds a user as a watcher of an issue by passing the account ID of the user, For example,5b10ac8d82e05b22cc7d4ef5, If no user is specified the calling user is added. See the documentationWritev0.0.25 -
Assign Issue
actionAssigns an issue to a user. See the documentationWritev0.0.24 -
Check Issues Against JQL
actionChecks whether one or more issues would be returned by one or more JQL queries. See the documentationRead-onlyv0.0.11 -
Count Issues Using JQL
actionProvide an estimated count of the issues that match the JQL. See the documentationRead-onlyv0.0.11 -
Create Custom Field Options (Context)
actionCreate a context for custom field options. See the documentation.Writev0.0.17
Triggers
-
New Event
triggerEmit new event when an event with subscribed event source triggered, See the documentationv0.0.25 -
New Issue Created Event (Instant)
triggerEmit new event when an issue is created. Note that Jira supports only one webhook, if more sources are needed please useNew Eventsource and select multiple events.v0.0.25 -
New Issue Deleted Event (Instant)
triggerEmit new event when an issue is deleted. Note that Jira supports only one webhook, if more sources are needed please useNew Eventsource and select multiple events.v0.0.25 -
New Issue Updated Event (Instant)
triggerEmit new event when an issue is updated. Note that Jira supports only one webhook, if more sources are needed please useNew Eventsource and select multiple events.v0.0.25
MULTI-APP
Works with more apps
The combinations customers connect alongside these two — nothing here is limited to a pair.
REFERENCE
Toolkit details
- x-pd-app-slug
- intercom,jira
- Primary app
- Intercom (intercom)
- Second app
- Jira (jira)
- Authentication
- OAuth + OAuth
- Available actions
- 52
- Available triggers
- 20