We need to submit tickets from our software to HubSpot. We already have a private App setup with multiple integrations.
We have tried two methods without luck:
1. Using the Ticket API Here we can create both tickets, associations, engagements, etc. but the tickets will not show in the "Help Desk" workspace, which is the place our support team works.
2. Using the old Legacy Form Submission API's Tried various approaches without luck. The V3 Legacy API cannot create form submissions with ticket fields, only contact and company fields. and it cannot add files. The V2 API is the same. The V4 API doesn't seem to have a "Submit Form data" endpoint.
So my question is: What is an actual working approach, if we need to submit tickets into the Help Desk Workspace automatically on behalf of customers (including file attachments).
@michaelrandrup - I offer up my approach to integrations of this sort in the hope that it may be helpoful to you.
- Focus on the forms submissions API to trigger the ticket creation action. I tend to feel that a direct ticket API integration exposes too many internal pipeline and status value dependencies to the external system
- Use only Contact and Company properties in the form setup. This can include a file or files
- Use the form submission to trigger a workflow that assembles the ticket data from the submitted properties on the Contact record.
- The ticket creation workflow can establish the right pipeline for the ticket (I often see cases where there are multiple options for handling), set up its status and stage, and assignment ownership on whatever basis makes sense. Submitted files from the form can be copied to specific file properties on the ticket record to support the issue.
Helpesk does have a particular quirk that I hope will be fixed soon in that it insists on conversation threads on a ticket to display properly. More basic ticket handling does not have this limitation.
@michaelrandrup - I offer up my approach to integrations of this sort in the hope that it may be helpoful to you.
- Focus on the forms submissions API to trigger the ticket creation action. I tend to feel that a direct ticket API integration exposes too many internal pipeline and status value dependencies to the external system
- Use only Contact and Company properties in the form setup. This can include a file or files
- Use the form submission to trigger a workflow that assembles the ticket data from the submitted properties on the Contact record.
- The ticket creation workflow can establish the right pipeline for the ticket (I often see cases where there are multiple options for handling), set up its status and stage, and assignment ownership on whatever basis makes sense. Submitted files from the form can be copied to specific file properties on the ticket record to support the issue.
Helpesk does have a particular quirk that I hope will be fixed soon in that it insists on conversation threads on a ticket to display properly. More basic ticket handling does not have this limitation.
Can you share an example request along with the internal values for your Pipeline? This may help other community members with troubleshooting.
Thanks for the additional information! — Jaycee
Join us on March 27th at 12 PM for the Digital Essentials Lab, an interactive session designed to redefine your digital strategy!
Engage with expert Jourdan Guyton to gain actionable insights, participate in live Q&A, and learn strategies to boost your business success. Don't miss this opportunity to connect and grow—reserve your spot today!
Did you know that the Community is available in other languages? Join regional conversations by changing your language settings !