Tod Sacerdoti : Also, do you have a separate account in the sandbox? I was required to create a new account for the sandbox with different credentials vs. my core account.
Tod Sacerdoti : You can sign up for a new payhere account on the Sandbox site.
Evyn Ecclesia : Hi Tod.
No I have not deployed the workflow, b/c I was assuming that the trigger (set in the prev step) would automatically deploy and run the next steps (without intervention)…
…And yes, I’ve established a separate Sandbox Acct for Payhere. In the Screenshot below,
in the bottom-left corner, you’ll see an orange bubble (just above the task bar) that says “Sandbox Environment” -which is where I’m pulling the API Key that is being used in SANDBOX REV Auth in PD.
Please advise.
Tod Sacerdoti : if you workflow isn’t deployed, the auth isn’t connected
Tod Sacerdoti : so, you need to deploy the new version
Tod Sacerdoti : you can turn the trigger off in the upper right if you don’t want the trigger to emit any events
Tod Sacerdoti : once you deploy, you can confirm if the auth is connected in you Connected Accounts
Tod Sacerdoti : is it listed as expected?
Evyn Ecclesia : Looks like an extra “sandbox” is showing up in the file name?
Please advise.
Evyn Ecclesia : I removed the “sandbox” just after the brace in the URL Code, and the Auth Step appears to have finally worked.
It looks like that’s what was causing the extra “sandbox” in the file name.
Hope you agree, and thanks.
Tod Sacerdoti : Yes, that was not added by us. If you create an action using Payhere it does not have the extra sandbox in the URL.
Evyn Ecclesia : Thank you very much Tod for your assistance in setting up, tweeking, and establishing this connection.
Working with you has been swift and informative.