Toggl Plan (Independent Publisher)

[Laskewitz]

Added the Toggl Plan connector which was requested by the one and only @natalie-pienkowska 👍🏼

When submitting a connector, please check the following conditions for your PR to ensure a smooth certification process.

• I attest that the connector works and I verified by deploying and testing all the operations.
• I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
• 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.

[Laskewitz]

Sorry - forgot to remove the number behind the connector title, fixed now.

[natalie-pienkowska]

Thank you for your submission, Daniel :) It is now officially in our hands. Looks like it passed all of our automated validations, so you will hear from @sriyen-msft (our awesome certification engineer) shortly once we completes all manual validations on his end.

[Laskewitz]

Fixed all descriptions.

[Laskewitz]

Sorry @sriyen-msft, this one was a mess. I somehow missed a bunch of descriptions. But now it's all good to go!

[sriyen-msft]

[[certify-connector]]

[sriyen-msft]

@Laskewitz Apologies for the delay in deployment of your connector, there were few challenges we saw while setting up OAUTH apps for your connector and all the issues were resolved and your connector is now being published to production regions and it is expected to completed with documentation by Wednesday, 1st September 2021. Please let us know if you have any questions. Thanks