| | Hello there. HubSpot answered the questions everyone kept asking about agents: what costs credits, who can build them and what happens when you hit your limit. Also today: shorter forms that fill themselves in, a CrowdStrike app that watches your portal's security, and why so many portals end up a mess. In today’s newsletter, we’ll get into: - Building and testing HubSpot agents is free, production runs use credits, and a run in progress finishes even if you hit your limit.
- Form shortening hides fields that enrichment data can fill in once a visitor types their email, so forms ask for less.
- Falcon Shield by CrowdStrike is new in the Marketplace, giving read-only checks on users, permissions and risky access in your account.
| |
|
| | 🤖 Your agent credit questions, answered. HubSpot's community team posted an Agent Hub and Agent Builder FAQ from its four live sessions. Building and testing agents is free, production runs use your plan's credits, and a run already underway finishes if you hit the limit, after which you pause, continue or buy more. Limits are set per agent or across all custom agents, and permissions can be admins only, everyone, or specific teams. 🔀 Why the new Workflow Builder is worth a look. The same FAQ explains that the new Workflow Builder can touch several objects in one flow, such as contacts, deals, tickets and custom objects, and can start from outside events like Google Sheets updates, Slack mentions or webhooks. It runs agents as steps and branches on their output. It is for Professional plans and up, and legacy workflows keep working, with migration tools coming soon. 📞 Sorting calls by keywords in their notes. A user wanted to trigger a workflow from call notes to set the call category by keyword. A community member showed the way: create a workflow from scratch, choose trigger manually, pick the Call object, then open enrollment criteria and select when filter criteria is met, where the call note properties are listed. Handy for anyone cleaning up call reporting. | |
|
| | ✂️ Shorter forms that fill in what you already know. A HubSpot Academy tip shows how form shortening hides fields that enrichment data can populate after a visitor enters their email, so people type less and your team still gets the details. Turn it on under Marketing, Forms, the updated form editor, then Settings and Form shortening. Worth testing on a busy demo or contact form this week. 🎓 Fast lead follow-up without feeling pushy. A marketer in higher education asks how others keep lead nurturing quick but not intrusive. A prospective student requests program information, and the reply should be fast, but they do not think every form fill should trigger the same sequence. If you branch nurture paths by intent or program, the thread is a good place to share how you set it up. 📨 Marketing emails that break when forwarded. A team saw a marketing email look fine on send but lose its formatting when forwarded. The community manager and another member explain that forwarding often makes the receiving email client reprocess the code and strip out responsive layout pieces, which is not unique to HubSpot. Their advice is to send the email to new people from HubSpot rather than forwarding it. | |
|
| | 🛡️ CrowdStrike brings a security watchdog to the Marketplace. New in the Marketplace, Falcon Shield by CrowdStrike offers ongoing security posture checks for your HubSpot account. It gets read-only visibility into users, permissions, teams, domains and security activity to spot risky access and misconfigurations. If your portal has grown lots of users and leftover admin rights, this is one way to keep an eye on it. ✅ No impact from the PHP security flaw. HubSpot's status page says it is aware of the recently disclosed PHP security vulnerability, that PHP is not part of its infrastructure, and that it knows of no impact on the platform or customers. The notice is marked resolved, and HubSpot says it will post an update if that changes. Useful to forward if a client's IT team asks. 🧹 Why every portal ends up a mess. An agency partner says they have lost count of the portals they have cleaned up, and the story is the same across companies and industries: nobody plans the mess, it builds up after the person who set everything up moves on. If you inherit a portal soon, start with an audit of properties, workflows and owners before adding anything new. | |
|
| | 💡 Two feature requests: social posts in ChatGPT and a fuller Workflows API. Two new requests on the Ideas board stand out. One asks to add social post drafting and scheduling to the ChatGPT connector, since website and blog publishing already work there. Another asks for the Workflows API to read and write settings that are UI-only today, because some API writes quietly wipe them. Add your vote if either one slows your team down. | |
|
| | Three remote roles posted in the last two weeks, each linked to its own posting with the source named. Each posting is linked from the source named on its line, with the date it was posted. Check the details on the posting itself. | |
|
|
|
