Skip to main content

Visibility in new data sources (APIs or otherwise)

Comments

6 comments

  • Paul

    Hey @jon-b2b_bi. Thanks for joining our new community forum. We’ll do a huddle on our end and get back to you on sharing info about new APIs and the roadmap.

    Meanwhile, any thoughts on new data sources you recommend?

    0
  • jon-b2b_bi

    Thanks Paul! At a minimum right now, I just noticed that the number of API data sources recently went from 61 to 62 and then I’m manually trying to figure out what’s been added so perhaps as a baby step, you can simply highlight ‘what’s new’ either in this community or via email or via the interface.

    Re: new data sources, I’m coming at it from the B2B space so there are two 800 pound gorillas in email/call tracking, i.e. Outreach.io & Salesloft. They both have plugins to Salesforce and APIs that would be useful.

    Then from a subscription business management perspective, you’ve got Stripe but there’s also Recurly, ChargeBee, and Zuora that all have APIs and cover about 90% of the SaaS world.

    0
  • Markus

    @jon-b2b_bi

    The best way to get insight into data sources is to create support tickets for each data source you are interested in. This way we can track them and also update you as they get released. I have gone ahead and created tickets for some of the data sources you mentioned. I do think it would be good moving forward to also have a section where people can request and see what others have requested to then upvote the requests.

    0
  • jon-b2b_bi

    Thanks @Markus but getting notifications on my requests when they are released is nice but what I’m really after is whether I should commit dev resource today or not based on some visibility for what your team is doing. If you tell me that Outreach.io API is not in the works and never will be, I’m OK with that and I’ll go build something myself. If you tell me that Outreach.io API is on the list but won’t be addressed for a year or 9 months or 6 months,etc. then that gives me a separate decision point. I’m assuming you’re getting requests all the time but it’s weighted according to the size of the customer (i.e. $) who have insight into your plans, e.g. recent Pendo integration. Perhaps I’m missing something as far as why you wouldn’t want to convey some transparency around your API dev schedule to the rest of your customers.

    0
  • Markus

    Hi Jon,

    Happy to discuss with you further.
    Will ping you via email to see what day/time works best to discuss.

    Regards,
    Markus

    0
  • Paul

    @jon-b2b_bi. Fyi - we’ve also now sharing our Changelog in the community, which includes new data sources. Check out the ‘changelog tag’: https://community.panoply.io/tags/changelog

    0

Please sign in to leave a comment.

Powered by Zendesk