Custom Connector with expiring API Key

(0) Share

Report

Posted on by Andrew - Davinci Te...

I'm continuing my previous thread as I try to build a custom connector to Dayforce with an expiring API key here.

I have had success without any issue using basic auth to the API but I would like to implement the expiring API key in production as it is more secure. Here is the flow I have set up already.

1. Get the updated Bear Token: Successful

2. Parse JSON to prepare the token: Successful

3. Create new Connection: successful

4. Add it to the running flow: Failed.

Flow save failed with code 'WorkflowRunActionInputsInvalidProperty' and message 'The 'inputs' of workflow run action 'Get_Flow' of type 'OpenApiConnection' should not have the property 'authentication'.'.

Looks like it's not liking the authentication property in the header.

I also don't know how to clean up the old connections. I would have hundreds of created connections before long.