BuilderPack
BuilderPack is a pack of 19 AI actions that installs into a HubSpot portal in a single OAuth step. Each action doubles as a workflow step and an Agent Builder tool, adding research, content generation and utility capabilities.
What is BuilderPack?
BuilderPack is a pack of AI actions for HubSpot, published by HubSpot Labs according to the footer of its site. It installs once per portal through HubSpot OAuth: there is no separate account to create and no API key to paste. Once installed, its 19 actions appear in two places — inside a workflow, under Add action > Connected apps, and on an Agent Builder agent, under the Actions tab.
The actions come in four groups. Company research holds three: Company Earnings Info (what a listed company said on an earnings call for a given quarter), Company Financial Profile (a market snapshot built from a ticker) and Domain Info (the owner and registration date of a domain). Social and web intelligence is the largest group with eleven: Get LinkedIn Activity, Get LinkedIn Posts, Get LinkedIn Company Posts, Get LinkedIn Company Profile, Get Instagram Profile, Get Instagram Followers, Recent Tweets, Google News Data, YouTube Channel Data, YouTube Search Results and YouTube Transcript. Content generation holds two, Generate Content (writing, summarising, reformatting) and Generate Image. Utilities holds three: Web Page Screenshot, Send Message (email) and Invoke Other Agent.
The documentation describes nine ready-made agent scenarios assembled from these actions: Account Intelligence, LinkedIn Prospect Research, LinkedIn Engagement Digest, Inbound Lead Due-Diligence, Instagram Influencer Vetting, Twitter/X Brand Pulse, YouTube Content Teardown, Generate Image and Live Web Research.
Access is gated by the HubSpot plan rather than by a price list: a Professional or Enterprise portal is required, because Agent Builder does not exist on Free or Starter portals. The publisher absorbs the running costs, stating that actions run on BuilderPack's infrastructure and are billed to it, not to the customer.
There is a lineage worth knowing. The address agent.ai now returns a permanent redirect to builderpack.com, and the privacy policy states that actions currently execute on agent.ai infrastructure operated by the same team. The site itself is spare: no pricing page, no about page, no social links, no image logo, and a noindex robots meta tag.
What it does
- Add 19 AI actions to a HubSpot portal in one installation, each usable both as a workflow step and as an Agent Builder tool
- Research a company: what it said on an earnings call for a given quarter, a market snapshot from its ticker, and the registrar record behind its domain
- Gather social and web intelligence from LinkedIn activity, posts, company pages and firmographics, Instagram profiles and followers, recent X posts and Google News
- Mine YouTube for channel data, search results and full video transcripts
- Generate written content with a selectable model, or generate an image from a description
- Run utilities: screenshot a web page, send an email, or delegate a task to another agent
- Feed each action a literal value, a CRM property token or the output of an earlier step, with long research calls executing asynchronously
When to use BuilderPack / When not to
A quick filter to help you decide if BuilderPack is the right fit.
When to use BuilderPack
- Go-to-market teams already running on HubSpot Professional or Enterprise, who want AI steps inside the workflows they already maintain
- Sales reps preparing a meeting: an account brief, LinkedIn prospect research and a conversation opener drawn from recent activity
- Marketing teams vetting Instagram influencers, tracking competitors on X and in the news, or tearing down YouTube content
- Revenue operations qualifying unknown inbound leads with domain age, a page screenshot and recent news coverage
- Agent Builder users who want ready-made tools to plug into an agent rather than integrations to code
When not to use BuilderPack
- HubSpot Free or Starter portals, where Agent Builder is not available and the pack has nowhere to run
- Teams working outside HubSpot: there is no standalone application and no public API, so the actions exist only inside a portal
- Organisations that need an availability commitment: the terms are 'as is', with no guarantee of uptime, and actions may be changed or withdrawn
- Buyers who require formal compliance guarantees, since no GDPR statement, DPA, subprocessor list or certification is published
- Workflows that send AI output straight to a customer, as the terms require a human to review the output first
How to use BuilderPack
A typical end-to-end flow, from setup to results.
- Check the prerequisite: a HubSpot Professional or Enterprise portal, and the right to install an app on it
- Install the pack and approve the requested scopes in HubSpot; the grant covers that one portal, and nothing is installed before approval
- Open a workflow, choose Add action, and pick BuilderPack under Connected apps
- Select the action you need and map its inputs: a typed value, a CRM property token, or the output of an earlier step
- Reuse the action's output tokens in the later steps of the same workflow
- For the agent route, create or open an agent in Agent Builder and add the BuilderPack tools from its Actions tab
- Run the agent from the Agent Inbox or from chat; the editor's test mode only simulates the tools, so real executions happen on the live surfaces
- Read each action's page for the exact fields expected, including the allowed values of closed-choice fields
- When a step misbehaves, open the workflow history, find the step and read its response; most failures are a missing required input or a malformed value
- To leave, first remove or replace the steps that use these actions, then uninstall the app from the portal's connected apps settings
Pros & Cons
Pros
- One installation, no API key and no extra account to manage
- Broad coverage in a single pack: LinkedIn, Instagram, X, YouTube, news, financial data, domain records, content, images, screenshots and email
- Execution costs are absorbed by the publisher rather than billed to the customer
- Every action has its own page listing the fields, the allowed values and an example
- A failed action returns a message instead of stopping the workflow, so the following steps keep running
- Long research calls execute asynchronously and do not block the workflow
- Nine agent scenarios are already documented, together with the actions that compose each one
Cons
- Locked to HubSpot: no standalone application, no public API, nothing usable outside a portal
- Free and Starter portals are excluded, since Agent Builder is not available there
- No GDPR information, no DPA, no subprocessor list and no stated hosting country
- No availability commitment: the publisher may modify, replace or withdraw an action at any time
- No pricing page at all — the commercial model rests on a single sentence of the install page
- A single support channel, one email address, on a domain (agent.ai) different from the site's own
- No about page, no named legal entity and no postal address anywhere on the site
Pricing & Plans
The site publishes no pricing page and no amount, currency or billing unit. Installation is free of charge and the cost of running the actions is borne by the publisher, which states that actions run on BuilderPack's infrastructure and are billed to it rather than to the customer. The only real expense is indirect: the pack requires a HubSpot Professional or Enterprise portal, a paid subscription priced by HubSpot and not by BuilderPack. No free trial is mentioned, and none would serve a purpose, the installation itself carrying no charge.
- there is a single level of access
- the pack installed into a HubSpot portal at no charge from the publisher
- a Professional or Enterprise portal is eligible
- a Free or Starter portal is not
- Installation is granted per portal
- and a second portal requires its own separate approval
Data, GDPR & hosting
A consolidated view of how BuilderPack handles your data.
GDPR overview
The site does not mention the GDPR anywhere: no claimed compliance, no legal basis, no Article 27 representative, no data protection officer. No DPA is published or offered, no subprocessor is named — third parties are described only by category, as 'a data provider' or 'an AI model provider' — and no hosting country or region is stated. No certification such as SOC 2 or ISO 27001 is mentioned. What does exist is narrower: the privacy policy, dated 12 August 2026, describes security measures (portal credentials stored encrypted, HubSpot requests signature-verified before being acted on, access limited to what an action needs) and opens a deletion route — contact the publisher with your portal ID to have stored execution records deleted. Uninstalling the app revokes access and stops processing. Anyone with a European compliance obligation will have to obtain the rest of these commitments directly from the publisher.
Who owns the data?
There is no separate BuilderPack account: the app is installed into a HubSpot portal and runs only when a workflow step or an Agent Builder agent invokes one of its actions. The publisher receives an access token identifying the portal, together with account and scope information, and stores the portal ID and the tokens needed to keep the connection alive. It also receives whatever the step passes in — mapped CRM property values such as a domain, a company name or message content — and records execution metadata: which action ran, when, for which portal and with what result. The customer decides which actions run and which CRM fields they receive; uninstalling revokes access and stops all processing.
Reuse rights
Inputs are used to run the requested action and return its result to the workflow or the agent that called it. Execution metadata is used to operate the service: diagnosing failures, handling support requests and measuring how the actions are used. The publisher states that it does not sell personal information and does not use customer CRM data to train models. Each action reaches out to an outside service — a LinkedIn lookup queries a data provider, a content action calls an AI model provider, a screenshot loads the page named in the step — and the input supplied travels to the provider that action depends on, under an agreement limiting what that provider may do with it. Actions currently execute on agent.ai infrastructure operated by the same team. Nothing on the site restricts what the customer does with the output returned to the portal, but the terms make the customer responsible for reviewing that output before relying on it or passing it on.
Data retention & training
Hosting summary
The site states no hosting country and no hosting region. The only infrastructure statement in the privacy policy is that actions currently execute on agent.ai infrastructure operated by the same team, which names a platform rather than a jurisdiction. No data centre, cloud provider or subprocessor is identified, and no certification is claimed. What is described is protection rather than location: portal credentials are stored encrypted, and requests coming from HubSpot are signature-verified before being acted on, with access limited to what an action needs. Outside anything the publisher declares, a network check made on 8 September 2026 resolved builderpack.com to 64.239.123.193, an anycast address in Amazon's AS16509 announced from the United States, while agent.ai resolves onto Cloudflare. That is an observation about where the website is served, not a statement about where CRM inputs, action outputs or execution metadata are processed and stored. Anyone with a data residency requirement should treat the jurisdiction as undetermined and ask the publisher directly.
Things to keep in mind
Risks and trade-offs to weigh before adopting BuilderPack.
- Send Message sends real email on your behalf: a wrong recipient means a message that has actually gone out, so check recipients before switching the workflow on
- Outputs mix third-party data with generated content, and nothing is guaranteed as to accuracy, freshness or fitness for purpose; the terms ask you to review the output before relying on it, and above all before sending it to a customer
- It is easy to let a plausible-looking account brief replace the reading and judgement a human would otherwise apply: the research is a starting point, not a verdict
- The social research actions query public personal data on LinkedIn, Instagram and X, and the customer carries the legal basis for doing so
- The actions depend on outside providers that change, and the publisher may modify, replace or withdraw an action; the service is supplied 'as is' and 'as available', with no uptime guarantee
- Acceptable use is your responsibility: no unauthorised data collection, no unsolicited bulk mail, no illegal or deceptive generated content, no circumventing a third-party service's terms
- Uninstalling without cleaning up leaves workflow steps in place that simply stop executing, quietly breaking automations that still look healthy
Setup & Integrations
Technical difficulty
Installation is trivial: one click, HubSpot OAuth, no separate account and no API key. Scope approval happens inside HubSpot, and nothing is installed until it is granted. The real effort comes afterwards, in mapping each action's inputs and chaining output tokens between workflow steps — helped by action pages that list the expected fields and the allowed values. No development skill is required: there is no code to write and no API to call. The only administrative prerequisite is a HubSpot Professional or Enterprise portal and the right to install an app on it.
Deployment
Integrations
Behind BuilderPack
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
Do I need a BuilderPack account?
Which HubSpot plan is required?
How many actions are included?
Where do the actions appear once installed?
How much does it cost?
Is my CRM data used to train models?
What happens if an action fails?
Why does a research action take so long?
How do I uninstall it?
How do I reach support?
Should you pick BuilderPack?
BuilderPack is an unapologetically narrow tool. If your revenue team already lives in HubSpot, it is genuinely useful and unusually well documented: nineteen actions, each with a page listing the exact fields, the allowed values and an example, plus nine agent scenarios showing how they combine. If you work anywhere else, it has nothing to offer — there is no standalone application and no public API.
The economics are unusual too. The publisher absorbs the execution costs, stating that actions run on its own infrastructure and are billed to it rather than to the customer. The only thing you pay for is the HubSpot plan itself, and a Professional or Enterprise portal is mandatory because Agent Builder does not exist below that line. That makes the pack cheap to try and easy to abandon.
The weak point is data governance. Nothing is published about the GDPR, about hosting locations, or about the providers the actions depend on — third parties appear only as categories, 'a data provider' or 'an AI model provider'. The privacy policy does commit to not training models on customer CRM data, encrypts portal credentials and offers deletion of execution records on request, but a European buyer with a real compliance obligation will have to ask for the rest directly.
Several signals point to a young product: the domain was registered on 28 February 2025, the terms and the privacy policy are both dated 12 August 2026, and the site carries a noindex robots tag. Add the redirect that leads here — the historic agent.ai address now points to BuilderPack — and the sensible posture is to try it on workflows you can afford to lose, and to verify that continuity before attaching a critical process to it.
- Choosing a selection results in a full page refresh.
- Opens in a new window.