MULTI-APP TOOLKIT
Build with FireCrawl + HubSpot
- Multi-app
- One MCP session
- 115 actions
- 27 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every FireCrawl and HubSpot 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": "firecrawl,hubspot",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: FireCrawl and HubSpot tools arrive
// together, each keyed by its own app's slug.
// e.g. run Crawl URL:
const result = await mcp.callTool({
name: "firecrawl-crawl-url",
arguments: {
url: "URL",
prompt: "Prompt",
},
})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 [firecrawlTools, hubspotTools] =
await Promise.all([
pd.components.list({ app: "firecrawl" }),
pd.components.list({ app: "hubspot" }),
])
// 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=firecrawl" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=hubspot" \
-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
FireCrawl
Connected account
HubSpot
Connected account
TOOLS
FireCrawl tools
The FireCrawl tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Crawl URL
actionCrawls a given URL and returns the contents of sub-pages. See the documentationWritev1.1.2 -
Extract Data
actionExtract structured data from one or multiple URLs. See the documentationWritev0.0.5 -
Get Crawl Data
actionObtains the status and data from a previous crawl operation. See the documentationRead-onlyv0.0.6 -
Get Extract Data
actionObtains the status and data from a previous extract operation. See the documentationRead-onlyv0.0.4 -
Map URL
actionMaps a given URL using Firecrawl's Map endpoint. Optionally, you can provide a search term to filter the mapping. See the documentationWritev0.0.3 -
Scrape Page
actionScrapes a URL and returns content from that page. See the documentationWritev1.0.4 -
Search
actionSearch the web and get full content from results. See the documentationRead-onlyv0.0.3
Triggers
No FireCrawl triggers are available yet.
TOOLS
HubSpot tools
The HubSpot tools this pairing puts in reach, each one running on your user's own connected account.
Actions top 8 of 108
-
Add Comment
actionAdds a comment to a thread. See the documentationWritev0.0.8 -
Add Contact to List
actionAdds a contact to a specific static list. See the documentationWritev0.1.4 -
Add Note to Contact
actionMCP and AI agents: Prefer this action when the user wants to leave a note on a HubSpot contact using a contact ID and note text. Exposes onlyhubspot,contactId, andnoteBody(no engagement-type step, noreloadProps, no dynamic HubSpot schema fields). Do not use Create Engagement for this workflow. For every writable note property or non-contact associations, use Create Note instead. See the documentationWritev0.0.6 -
Archive Thread
actionArchives a thread (soft delete). The thread is hidden from active views but can be restored via the HubSpot UI or by listing archived threads. See the documentationWritev0.0.5 -
Batch Create Companies
actionCreate a batch of companies in Hubspot. See the documentationWritev0.0.18 -
Batch Create or Update Contact
actionCreate or update a batch of contacts by its ID or email. See the documentationWritev0.0.32 -
Batch Update Companies
actionUpdate a batch of companies in Hubspot. See the documentationWritev0.0.18 -
Batch Upsert Companies
actionUpsert a batch of companies in Hubspot. See the documentationWritev0.0.17
Triggers top 4 of 27
-
Deleted Blog Posts
triggerEmit new event for each deleted blog post.v0.0.47 -
New Company Property Change
triggerEmit new event when a specified property is provided or updated on a company. See the documentationv0.0.40 -
New Contact Added to List
triggerEmit new event when a contact is added to a HubSpot list. See the documentationv0.0.19 -
New Contact Property Change
triggerEmit new event when a specified property is provided or updated on a contact. See the documentationv0.0.43
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
- firecrawl,hubspot
- Primary app
- FireCrawl (firecrawl)
- Second app
- HubSpot (hubspot)
- Authentication
- API key + OAuth
- Available actions
- 115
- Available triggers
- 27