Hey @sasha.sochka, the rules are not run when you click on the ‘Try’ button of the connection which must be why you are seeing this. Can you try to login with a sample app, so the full authentication flow is executed?
Which ‘Try’ button is this about? The ‘Try’ button below the rule editor will run the rule, and the ‘Try’ button next to a connection will initiate a login with the connection - but none of them will do the other thing.
it does not get added to the user profile data
Our default rule does not save the incoming email in the user’s profile, but stores it temporarily so it can get added to the ID token. If you request an email claim in the scope, you should see the email in the token.
If you are not certain that Twitter is sending the email or not, you can add a console.log in the rule after it is obtained and watch the logs using the Real-time Webtask Logs extension.
What is the correct way to actually save the email in the profile? Can we do that through the rule as well? Maybe there is some example when we can modify the profile saved to the DB on user creation?
As this topic is related to Rules - Hooks - Actions, I’m excited to let you know about our next Ask me Anything session in the Forum on Thursday, January 18 with the Rules, Hooks and Actions team on Rules & Hooks and why Actions matter! Submit your questions in the thread above and our esteemed product experts will provide written answers on January 18. Find out more about Rules & Hooks and why Actions matter! Can’t wait to see you there!