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.

  • Home
  • Get Help
  • How Do I
  • Issue with Okta Account Creation Zapier - ‘alternate id’ appears instead of actual value

Hi friends,


I have an Okta Zap set up to make a Trainerize account when an Okta account is created.

I can see the user email under ‘alternade.id’, but when it goes off and sends it to Trainerize, it just shows ‘alternate id’ instead of the actual value.

https://cdn.zapier.com/storage/photos/00f986ec05b113267f3099d070e141f7_3.png

Would love some support on this.


Side note, I wish there was a way to specify which group i assign a user to on the Okta assign user group event, instead of only being able to track any user being added to a group​​​​​​​

Hey@amlfitco developer, 

Thanks for reaching out about this and welcome to the Community! :)

It appears you’ve also reached out to our Support Team who identified that this is related to a known bug with the Okta integration where the structure for the live data is in a different format to the structure of the sample data. This causes fields not to be found when the Zap runs live, so no data can be passed over to the next step. You’ve been added to the list of affected users so we’ll be in touch by email as soon as it’s resolved.

In the meantime, manually specifying the alternade.id field using custom pill mapping, that follows the structure of the live data, should allow the Zap to send the alternate id value over to Trainerize. For example: 

{{123456789__data__events_]targetv]alternateId}}

123456789 in the above example would need to be replaced by the Node ID for the Okta step in the Zap.

More details on how to get the Node ID and use a custom pill mapping can be found here: 


Hope that helps!

Just circling back in here to share that the bug has been resolved! 😁🎉

The Okta app has been updated and now the fields that are pulled through in the test record samples match the fields are received when the Zap runs live. In order to take advantage of this fix you’ll want to ensure your Zap is running the latest version of the Okta app on Zapier. 

That said, if you experience any issues with it please do reach out in the Community to let us know. In the meantime, happy Zapping! ⚡️

Terms & Conditions