Workable (Independent Publisher) (#2172)

* Dev
* Update Readme.md

* Add files via upload

* Update apiDefinition.swagger.json

* Update apiProperties.json

* Update apiProperties.json

* Update Readme.md

* Update apiDefinition.swagger.json

* Update apiDefinition.swagger.json

* Update apiDefinition.swagger.json

* Update apiDefinition.swagger.json

* Update apiDefinition.swagger.json

---
### 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](https://forms.office.com/pages/responsepage.aspx?id=KtIy2vgLW0SOgZbwvQuRaXDXyCl9DkBHq4A2OG7uLpdUMTFJWFFGVUxBNUFZQjZWRUdaOE5BMFkwNS4u).

- [ ] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
- [ ] 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 attest that I have added response schemas to my actions, unless the response schema is dynamic.
- [ ] 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.

* Workable (Independent Publisher)

* Workable (Independent Publisher)

* Workable (Independent Publisher)

* Workable (Independent Publisher)

* Workable (Independent Publisher)

* requested changes

* requested changes

* Updated boolean fields

* Updated connectionParameters to be "api_key". API key provided was not recognize correctly.

* Delete settings.json

not needed
This commit is contained in:
David Kjell 2022-12-21 23:11:33 +01:00 коммит произвёл GitHub
Родитель 606466640f
Коммит 464a91e5dc
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
2 изменённых файлов: 2 добавлений и 2 удалений

Просмотреть файл

@ -1705,7 +1705,7 @@
"parameters": {},
"responses": {},
"securityDefinitions": {
"ApiKey": {
"API Key": {
"type": "apiKey",
"in": "header",
"name": "Authorization"

Просмотреть файл

@ -1,7 +1,7 @@
{
"properties": {
"connectionParameters": {
"ApiKey": {
"api_key": {
"type": "securestring",
"uiDefinition": {
"displayName": "Workable API Key",