RECRUITERFLOW API KEY ERROR

Hello,

Thank you for the detailed explanation.

To help us investigate why the Recruiterflow action appears to be using a different API token than the one currently configured, could you please share the URL of the affected workflow?

Once we have the workflow URL, we will review the connection configuration, action setup, and task history to determine whether an old connection is being referenced or if there is another issue causing the authentication error.

We look forward to your response.

Hrishabh Tiwari:
Hello,Thank you for the detailed explanation.To help us investigate why the Recruiterflow action appears to be using a different API token than the one currently configured, could you please share the URL of the affected workflow?Once we have the workflow URL, we will review the connection configura

https://connect.pabbly.com/v2/app/workflow/share/XRUCMAVSAmFTGQVvA2ZXcA0ZAgYAWgk1Bx4EFgQLXSVVG1IpVBVbMV8TUDpVGlMyVh8GbABcU2oLH1ZSAVcJelVbCBpSUQd9VBkCeQBNX2xdAwIqBWQ#

Hello Helal,

Thank you for trying that out.

Since switching to a completely new connection is still returning the exact same error, it appears the old token reference might be stubbornly cached or there could be an issue with how the API key is being transmitted to Recruiterflow's endpoints.

To help us investigate this deeper and run a backend test, could you please let us know the following?

1. Share the Token Securely: Are you comfortable sharing the active API token with us? If yes, please let us know, and we will send over a private, secure link where you can safely submit your credentials (please do not post them directly on this public forum).

2. Test via API Request: In the meantime, could you please try adding an API Request by Pabbly action step right before your Recruiterflow step? Set it to a GET request using your new token to see if it successfully authenticates or returns the same error. This will help us isolate whether the issue is specific to the Recruiterflow integration module itself.

Looking forward to your update!

Hrishabh Tiwari:
Hello Helal,Thank you for trying that out.Since switching to a completely new connection is still returning the exact same error, it appears the old token reference might be stubbornly cached or there could be an issue with how the API key is being transmitted to Recruiterflow's endpoints.To help us

I'll just send you the API Key so you can check on your end. Please share a secure private link where I can send it.

Hello Helal,

Thank you for your cooperation.

I have generated and sent a secure, private credentials link to your registered email address ([email protected]). You should also see a "Request credentials" or private link notification directly within this support thread.

Please click on that secure link to safely submit your active Recruiterflow API token.

Looking forward to your update!

Hrishabh Tiwari:
Hello Helal,Thank you for your cooperation.I have generated and sent a secure, private credentials link to your registered email address ([email hidden]). You should also see a "Request credentials" or private link notification directly within this support thread.Please click on that secure link to s

API key sent. Please check

Hello Helal,

Thank you for providing the API key safely.

We have successfully received the credentials and have escalated this case to our technical team for a deeper backend investigation to find out why the workflow is persisting with the old token.

We will update you here as soon as we have a resolution or further insights from them.

Hrishabh Tiwari:
Hello Helal,Thank you for providing the API key safely.We have successfully received the credentials and have escalated this case to our technical team for a deeper backend investigation to find out why the workflow is persisting with the old token.We will update you here as soon as we have a resolu

How long is the turnaround time? I need to set up this automation ASAP

Hi Helal,

Our technical team has successfully investigated and resolved the issue with your Recruiterflow connection.

The workflow was previously persisting with an older token configuration, but we have refreshed the backend setup. Your active API key is now properly recognized, and the connection is fully stabilized.

Please try running a test with your RECRUITERFLOW (create a candidate) action step now, and let us know if everything functions smoothly on your end!