MULTI-APP TOOLKIT
Build with Lucca + Salesforce
- Multi-app
- One MCP session
- 68 actions
- 15 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every Lucca and Salesforce 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": "lucca,salesforce_rest_api",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: Lucca and Salesforce tools arrive
// together, each keyed by its own app's slug.
// e.g. run Approve Or Deny Leave Request:
const result = await mcp.callTool({
name: "lucca-approve-leave-request",
arguments: {
leaveRequestId: "Leave Request ID",
approved: true,
},
})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 [luccaTools, salesforceRestApiTools] =
await Promise.all([
pd.components.list({ app: "lucca" }),
pd.components.list({ app: "salesforce_rest_api" }),
])
// 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=lucca" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=salesforce_rest_api" \
-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
Lucca
Connected account
Salesforce
Connected account
TOOLS
Lucca tools
The Lucca tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Approve Or Deny Leave Request
actionApprove or Deny a pending leave request. See the documentationWritev0.0.2 -
List Department ID Options
actionRetrieves available options for the Department ID field.Read-onlyv0.0.1 -
List Leave Request ID Options
actionRetrieves available options for the Leave Request ID field.Read-onlyv0.0.1 -
List Legal Entity ID Options
actionRetrieves available options for the Legal Entity ID field.Read-onlyv0.0.1 -
List Nationality Options
actionRetrieves available options for the Nationality field.Read-onlyv0.0.1 -
List User ID Options
actionRetrieves available options for the User ID field.Read-onlyv0.0.1 -
Update User Info
actionUpdate profile or HR information for an existing user. See the documentationWritev0.0.2
Triggers
-
New Expense Report Created
triggerEmit new event when a new expense report is created by an employee. Useful for automating approval or finance workflows. See the documentationv0.0.1 -
New Leave Request
triggerEmit new event when a new leave request is submitted by an employee. See the documentationv0.0.1 -
New User Created
triggerEmit new event when a new user (employee) is created in Lucca. See the documentationv0.0.1
TOOLS
Salesforce tools
The Salesforce tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 61
-
Add Contact to Campaign
actionAdd an existing contact to an existing campaign as a campaign member. Use Find Records onContactand onCampaignto look up the two IDs first. The contact must already exist - use Create Contact if it does not. See the documentationWritev0.1.9 -
Add Lead to Campaign
actionAdd an existing lead to an existing campaign as a campaign member. Use Find Records onLeadand onCampaignto look up the two IDs first. The lead must already exist - use Create Lead if it does not. See the documentationWritev0.1.9 -
Convert SOAP XML Object to JSON
actionConvert a SOAP XML payload received from Salesforce into JSON. Use this on the raw body delivered by an outbound-message trigger; it makes no API call. Every other Salesforce action already returns JSON, so this is only needed for outbound-message workflows. See the documentationRead-onlyv0.0.13 -
Create Account
actionCreate a Salesforce account (a company or organization record). Use Describe Object onAccountto discover which fields your org requires before calling. For example,NameAcme Corpcreates a minimal account and returns its new record ID. See the documentationWritev0.4.1 -
Create Accounts (Batch)
actionCreate many Salesforce accounts in one job using Bulk API 2.0. Use this instead of Create Account when inserting more than roughly 200 records - it is asynchronous and returns a job ID, not the created records. Poll the job in Salesforce to confirm completion; a successful response means the job was accepted, not that every row loaded. Input is a CSV file - supply a path under/tmpor a URL to download it from, with a header row of Salesforce field API names. See the documentationWritev0.0.8 -
Create Attachment
actionAttach a file to an existing Salesforce record (classicAttachmentobject). Use Find Records to get the parent record ID first. For newer orgs prefer Salesforce Files - use Insert Blob Data withContentVersioninstead. See the documentationWritev0.6.1 -
Create Campaign
actionCreate a Salesforce marketing campaign. Use Add Contact to Campaign or Add Lead to Campaign afterwards to populate its members. For example,Name: "Summer 2026 Webinar"creates the campaign and returns its ID. See the documentationWritev0.3.9 -
Create Case
actionCreate a Salesforce support case (a customer issue or request). Use List Cases to check whether a matching case already exists before creating a duplicate. After creating, use Create Case Comment to add notes or List Case Feed Items to read its activity. See the documentationWritev1.0.1
Triggers top 4 of 12
-
Case Updated (Instant, of Selectable Type)
triggerEmit new event when a case is updated. See the documentationv0.0.13 -
Email Template Updated (Instant, of Selectable Type)
triggerEmit new event when an email template is updated. See the documentationv0.0.13 -
Knowledge Article Updated (Instant, of Selectable Type)
triggerEmit new event when a knowledge article is updated. See the documentationv0.0.13 -
New Case (Instant, of Selectable Type)
triggerEmit new event when a case is created. See the documentationv0.0.13
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
- lucca,salesforce_rest_api
- Primary app
- Lucca (lucca)
- Second app
- Salesforce (salesforce_rest_api)
- Authentication
- API key + OAuth
- Available actions
- 68
- Available triggers
- 15