Recent searches


No recent searches

How do I provide feedback for the WFM Public API EAP?



Posted Feb 01, 2024

Join Our Community Forum for WFM Public API EAP Feedback

We’re excited about our community forum, a hub for engaging discussions and valuable feedback. We encourage you to join in, follow the latest topics, share your insights, or pose questions. When there’s buzz around a specific topic, especially related to the new WFM Public API Early Access Program (EAP), we’ll highlight it to gather diverse perspectives. Your thoughts and questions are welcome anytime, helping us shape this EAP together.

How to Provide Impactful Feedback

Your input is crucial, covering the good, the concerns, and suggestions for improvement. To foster a forum brimming with productive dialogue, we need a sprinkle of effort from everyone involved. Just leave a comment below.

Make your feedback impactful by considering these steps:

  • If something about the WFM Public API doesn't sit right with you or you see room for enhancement, take a note. Reflect a little before sharing.
  • Aim for clarity in your feedback. Explain what you like or dislike and how things might be fine-tuned.
  • Patience is appreciated as we respond to queries and comments.
  • Civility is our cornerstone—avoid sarcasm, disrespect, and offensive language. We're here to ensure discussions stay respectful.

Our goal is to make this forum the ideal place for all customers to share and discuss feedback specifically on the WFM Public API EAP. We’re looking for a mix of formal insight and casual exchange to create a welcoming and productive environment.


0

6

6 comments

image avatar

Jahn

Zendesk LuminaryCommunity Moderator

Hi Samanta Velho - Is there any images on the article you sent or something wrong with the file?

0


Hi Jahn,

 

I just sent you a new file that does not have any redering issues. Please check and let me know if everything's okay.

 

Thanks!

0


Hi,

Today I had the chance to review the documentation, and the feedback I can give is that I'd like it to be more complete and have more endpoints. For example, some things I find missing are:

  • Agents with Tymeshift active: extracting lists, creating new ones, etc.
  • Information about which team, location, and workstreams team members belong to, and the ability to make updates.
  • Workstreams, general tasks, time off reasons: getting lists, creating, and updating.

Let me know if you need further details!

0


Hi Rosa Lopez!

Thanks for your feedback, we appreciate it. 
The endpoints referred by you that are now missing on our WFM API, are owned by other Product Managers on the WFM organization but , I will add them to this thread so that they are aware of your input. 
 

CC: Maksym Shynkarenko, Rita Goncalves  Tiago Magalhaes please note Rosa's feedback shared here!

Thanks!

1


Samanta Velho  Here's some quick feedback that I have from the time I spent integrating this API into our data cube.

  • Doesn't make a lot of sense to have the relationships inside the Reports endpoint data.  Those are static so essentially the endpoint is returning redundant data on every page.  This is super inefficient for both the requester and Zendesk having to process extra data.  It seems like this would be better suited to be sent via a separate endpoint so that the requester can decide if they want that information refresh, and only once not once for every page in the report.
  • Only being able to pull one day at a time worked well for me, especially since my data pulls are automated.  Sure, it takes a bit of time to seed the data cube but moving forward shouldn't be an issue.  What was a bit unclear was why the API wouldn't let me pull data from today though.  Ideally, I would want to set my automation up to pull the current day.  To be able to report on real time data.
  • This is probably outside the scope of this EAP but I'd be great to see some more endpoints dealing with creating and reporting on time-off requests.  We love the time-off request system in Zendesk and would like to hook it into Paycom to update time cards with approved time off requests.

0


Hi Chris,

 

Thank you for all the feedback you provided! I’m glad to hear that it aligns with the insights we’ve been receiving from other early access participants. Here’s a bit more detail on your points:

  1. Relationships in the Reports Endpoint: We’ve received similar feedback regarding the relationships in the Reports endpoint. One of the planned improvements is to create a user management endpoint that will contain the user data currently available only in the relationships section. Additionally, we’re looking to develop endpoints for workstreams and general task information, which will help ensure everything can be properly mapped. We’re still discussing when we can start working on these improvements, so we don’t have an ETA just yet.
  2. Data Pulls and Real-Time Data: We’ve noted that many participants in the early access program would like the ability to collect more than one day of data. The ability to pull real-time data is also on our roadmap. We’re working to understand the most pressing needs and prioritize improvements accordingly.
  3. Time-Off Requests: This is related to both the WFM Public API and our integrations work. We’re currently developing a time-off endpoint in the WFM Public API and working on an integration with an HRIS system (though it’s not Paycom). Once we have that integration up and running, we’ll be looking into other possible integrations, and the process should be quicker due to the learnings from our first integration.

    CC: Maksym Shynkarenko Rita Goncalves Tiago Magalhaes Joanna Zoła Copying my colleagues that work with other areas of our Product so that they are also aware of your feedback.

Thanks again for your valuable input! If you have any more thoughts or questions, feel free to share.

Best,
Samanta

0


Please sign in to leave a comment.

Didn't find what you're looking for?

New post