Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessing Ticket Object ID in Hubspot Trigger Node #9400

Closed
codisfy opened this issue May 14, 2024 · 3 comments
Closed

Accessing Ticket Object ID in Hubspot Trigger Node #9400

codisfy opened this issue May 14, 2024 · 3 comments
Labels

Comments

@codisfy
Copy link

codisfy commented May 14, 2024

Bug Description

I'm having trouble getting a Hubspot-based workflow working with the trigger node using the "Ticket Created" event. The issue I'm facing is that I'm unable to retrieve the ObjectId (the ticket's ID) in the payload.

After researching, it seems that the ObjectId might be removed if it's not related to a Deal, Company, or Contact. However, I'm wondering if there's any way we can expose the ObjectId? Are there any potential downsides to doing so?

To Reproduce

Setup a Hubspot App

Use the Trigger Node with Ticket Created event

Send a test payload and see that ObjectId is missing (image)

image

Expected behavior

If there are no constraints, the node should allow access to ObjectId, this will help to fetch the ticket details using another node.

Operating System

Ubuntu 22.04

n8n Version

1.40.0

Node.js Version

20

Database

SQLite (default)

Execution mode

main (default)

@Joffcom
Copy link
Member

Joffcom commented May 15, 2024

Hey @codisfy,

Thanks for letting us know about this, I have popped in a PR that should resolve it. Once reviewed it will be merged and available in a future release.

@codisfy
Copy link
Author

codisfy commented May 15, 2024

Thank you! Much appreciated!

@janober
Copy link
Member

janober commented May 22, 2024

Fix got released with n8n@1.43.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants