Form Event action fires but submissions never reach HubSpot (same request via curl works)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- api
Research direction
Start at the handleFormEvent entry point and trace its manager.fetch call, then inspect the manifest change in commit 1661a33a for the server_network_requests permission. Reproduce the hosted Form Event submission and compare the request and response with the working curl request. Done means the deployed component reliably reaches HubSpot and failures are observable.
Written by the indexing model from the issue text.
Description
We set up a Form Event action on hosted Zaraz (tool created July 2026) with a valid HubSpot form GUID and email/firstname mapped from a zaraz.track() call. The debugger and Logpush show the action firing with a clean payload, but no submission ever arrives in HubSpot. Sending the identical body to api.hsforms.com/submissions/v3/integration/submit/{portal}/{formGuid} with curl returns 200 and works. This looks a lot like #7, which describes the same pattern for the events action: it fires, but nothing arrives.
Two things we noticed while trying to debug this. They may or may not be the cause:
handleFormEventcallsmanager.fetch()without awaiting it or checking the response, so if the request fails or never happens, there's nothing to see anywhere. Even just awaiting it and logging non-2xx responses would have saved us a lot of guesswork.- The manifest gained a required
server_network_requestspermission in 1661a33a (April 2024), but a freshly created tool on hosted Zaraz doesn't show any such permission in the dashboard. We couldn't tell whether the deployed build includes that manifest.
Happy to share debugger captures, Logpush rows, and repro details if useful.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from managed-components/hubspot
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
managed-components/hubspot#10 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
managed-components/hubspot#7 · 3 comments ·
All issues in managed-components/hubspot
Similar issues
-
area:plugins area:security area:skills bug has repro
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
anthropics/claude-code#105911 ·
Maintainers usually reply within 1 day
-
openspec-apply-change skill: when blocked, may select a ready artifact unrelated to missingArtifactsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Fission-AI/OpenSpec#2165 ·
Maintainers usually reply within 1 day
-
🐞 bug 🧐 unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Tencent/tdesign-vue-next#7032 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gnosis/gnosis_vpn#661 ·
Maintainers usually reply within 1 day
-
content-freshness: staleOwnedContent doc comments still say 'complete receipt' (follow-up to #7912)Opentriage:bug-verified
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day