FLOW-127: hotfix for connect configuration creation issues

[sriharip-docusign]

---

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)

If this is your first time submitting to GitHub and you need some help, please sign up for this session.

Please note that we are experiencing a significant delay due to a high volume of connector submissions. It may take 1-2 weeks for us to provide comments for your connector.

• [x ] I attest that the connector works and I verified by deploying and testing all the operations.
• [x ] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
• [x ] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
• [ x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
• If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

• I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
• Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
• Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
• If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

[sriharip-docusign]

The connect configuration flow only runs partially because of an issue where Microsoft webhook endpoint returns a 404 error.

The email step is not invoked because of the issue in Microsoft end related to webhook invocation, but the first step runs correctly.

However, the connect configuration is created in the backed when the flow is saved.

Envelope Sending successful screenshots