MULTI-APP TOOLKIT
Build with FlowiseAI + Jira
- Multi-app
- One MCP session
- 40 actions
- 4 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every FlowiseAI 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": "flowiseai,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: FlowiseAI and Jira tools arrive
// together, each keyed by its own app's slug.
// e.g. run Make Prediction:
const result = await mcp.callTool({
name: "flowiseai-make-prediction",
arguments: {
flowId: "Flow ID",
question: "Question",
},
})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 [flowiseaiTools, jiraTools] =
await Promise.all([
pd.components.list({ app: "flowiseai" }),
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=flowiseai" \
-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
FlowiseAI
Connected account
Jira
Connected account
TOOLS
FlowiseAI tools
The FlowiseAI tools this pairing puts in reach, each one running on your user's own connected account.
Triggers
No FlowiseAI triggers are available yet.
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
- flowiseai,jira
- Primary app
- FlowiseAI (flowiseai)
- Second app
- Jira (jira)
- Authentication
- API key + OAuth
- Available actions
- 40
- Available triggers
- 4