Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

hello ! How to create ticket in hubspot with a bot landbot by zapier ?

  • January 15, 2020
  • 6 replies
  • 188 views
M

Capture d’écran 2020-01-15 à 11.24.10.png


Best answer by PaulKortman

@Modegra Based on what I can read from the Hubspot API documentation here: https://developers.hubspot.com/docs/methods/tickets/create-ticket it looks like the issue you're having is that the hs_pipeline needs to be a number, aka the ID of the pipeline, and then your pipeline stage will also be a number, 1 2 3 or 4. Those numbers correspond to the following found here.

For the hs_pipeline_status property, the default stage IDs are:

- New is 1

- Waiting on contacts is 2

- Waiting on us is 3

- Closed is 4

So as @Danvers pointed out if you were to create a different (temporary) zap that had a trigger of "new ticket" and looked at the sample data you'd be able to see that both the pipeline and the pipeline stage are numbers. Currently you're setting the Pipeline to "Senegal" which is not a number.

Funny how the hubspot API is choking on the pipeline stage and not the pipeline id.


This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

6 replies

AndrewJDavison
Forum|alt.badge.img+11
  • AndrewJDavisonZapier Solution Partner
  • Zapier Solution Partner
  • January 15, 2020

Hi @Modegra

Welcome to the community!

So far, you're doing well - click "Continue" and on the next page you'll be able to configure the fields of the ticket.


Find out more and hire me: https://zapier.com/partnerdirectory/andrewjdavison (andrew@andrewjdavison.com)
M
  • Modegra
  • Author
  • January 15, 2020

Thank you @AndrewJDavison_Luhhu !

I hope you're fine ..

I was do it, but , i have get difficulties for configure some fields in "Customize Ticket" section.  I don't find the kind of input ( value ) who can corresponded to Ticket Pipeline Stage.

Capture d’écran 2020-01-15 à 12.35.51.png

Wherever ! indicate a value let's go from 1- 4 , i get an error message


Capture d’écran 2020-01-14 à 15.37.59.pngKnowing that , when i indicate any value this following message is displayed...

Capture d’écran 2020-01-15 à 12.48.20.png








Danvers
Forum|alt.badge.img+12
  • DanversZapier Staff
  • Zapier Staff
  • January 15, 2020

It looks like

Pipeline stage may need to be both

-

'[

,

,

,

]' looks like


It might be helpful here to build a Zap with the 'New ticket' trigger, so that you can look at the trigger sample to see how the Ticket Pipeline Stage information is formatted. Do you think you could give that a go and if you're not sure what the format is, take a screenshot of it and share it here so we can take a look 😊


    PaulKortman
    Forum|alt.badge.img+10
    • PaulKortmanZapier Solution Partner
    • Zapier Solution Partner
    • Answer
    • January 15, 2020

    @Modegra Based on what I can read from the Hubspot API documentation here: https://developers.hubspot.com/docs/methods/tickets/create-ticket it looks like the issue you're having is that the hs_pipeline needs to be a number, aka the ID of the pipeline, and then your pipeline stage will also be a number, 1 2 3 or 4. Those numbers correspond to the following found here.

    For the hs_pipeline_status property, the default stage IDs are:

    - New is 1

    - Waiting on contacts is 2

    - Waiting on us is 3

    - Closed is 4

    So as @Danvers pointed out if you were to create a different (temporary) zap that had a trigger of "new ticket" and looked at the sample data you'd be able to see that both the pipeline and the pipeline stage are numbers. Currently you're setting the Pipeline to "Senegal" which is not a number.

    Funny how the hubspot API is choking on the pipeline stage and not the pipeline id.


    Need Additional help? Feel free to reach out here: https://zapier.com/experts/connex-digital/
    M
    • Modegra
    • Author
    • January 15, 2020

    Hello @Danvers, thank you for your great and great idea.

    finaly! I found another way by dint of testing.

    In the "Ticket Pipeline" field, I chose "Senegal" Pipeline in place of « Custom value", and automatically, the values ​​I was looking for were displayed in the "Ticket pipeline stage" field

    Thank you for your assistance


      Danvers
      Forum|alt.badge.img+12
      • DanversZapier Staff
      • Zapier Staff
      • January 16, 2020

      That's great! Nice job, @Modegra 🙌


      Terms & ConditionsAccessibility statement