Proposal - Airtable Cloud (Independent Publisher)

[BitcotDev]

---

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.

• 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.

[BitcotDev]

@microsoft-github-policy-service agree [company="{your company}"]

@microsoft-github-policy-service agree [company="Bitcot technologies"]

[BitcotDev]

@BitcotDev the command you issued was incorrect. Please try again.

Examples are:

@microsoft-github-policy-service agree

and

@microsoft-github-policy-service agree company="your company"

@microsoft-github-policy-service agree
@microsoft-github-policy-service agree company="Bitcot technologies"

[troystaylor]

Hello @BitcotDev, there is already an established Airtable connector. Did you consider extending that connector as there are overlapping actions?

CC: @last72

[BitcotDev]

Hello @BitcotDev, there is already an established Airtable connector. Did you consider extending that connector as there are overlapping actions?

CC: @last72

Hello @microsoft-github-policy-service agree
Thank you for pointing that out. We are aware of the existing Airtable connector, but our custom connector was designed to address specific use cases and actions that are not covered by the existing one. The current Airtable connector offers only 5 action items, whereas our enhanced version includes 13 action items, with just 5 overlapping and 8 new ones.
We plan to further develop our custom connector with even more action items in the future. Could you please advise us on the process for extending the existing connector, and how we can contribute to enhancing its functionality?

[troystaylor]

@BitcotDev I would suggest adding your additional actions to the existing Swagger (https://github.com/microsoft/PowerPlatformConnectors/tree/dev/independent-publisher-connectors/Airtable) and having @last72 review the changes.

[vmanoharas]

Hello @BitcotDev @troystaylor, I will wait and watch your conversation before approving this connector, as I saw that two PRs are closed and open this PR.

@BitcotDev - Kindly finalize and let me know to proceed further, as @troystaylor mentioned Airtable connector is already present, please add your additional actions and triggers instead of creating new connector.

[BitcotDev]

Hello @BitcotDev @troystaylor, I will wait and watch your conversation before approving this connector, as I saw that two PRs are closed and open this PR.

@BitcotDev - Kindly finalize and let me know to proceed further, as @troystaylor mentioned Airtable connector is already present, please add your additional actions and triggers instead of creating new connector.

Hello Team,
We want to publish the connector by our name. Please let us know what we need to do in this case.

[troystaylor]

Hello @BitcotDev @troystaylor, I will wait and watch your conversation before approving this connector, as I saw that two PRs are closed and open this PR.
@BitcotDev - Kindly finalize and let me know to proceed further, as @troystaylor mentioned Airtable connector is already present, please add your additional actions and triggers instead of creating new connector.

Hello Team, We want to publish the connector by our name. Please let us know what we need to do in this case.

You are welcome to contribute to the existing connector, but you cannot publish a new connector for the same service. Please refer to both of these pages:
https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip#prepare-and-submit-your-connector-for-certification
https://github.com/microsoft/PowerPlatformConnectors/wiki/Independent-Publisher-Connector-Group-%22Manifesto%22

[BitcotDev]

Hello @BitcotDev @troystaylor, I will wait and watch your conversation before approving this connector, as I saw that two PRs are closed and open this PR.
@BitcotDev - Kindly finalize and let me know to proceed further, as @troystaylor mentioned Airtable connector is already present, please add your additional actions and triggers instead of creating new connector.

Hello Team, We want to publish the connector by our name. Please let us know what we need to do in this case.

You are welcome to contribute to the existing connector, but you cannot publish a new connector for the same service. Please refer to both of these pages: https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip#prepare-and-submit-your-connector-for-certification https://github.com/microsoft/PowerPlatformConnectors/wiki/Independent-Publisher-Connector-Group-%22Manifesto%22

Please let us know if using entirely different triggers and actions not currently employed by any existing connector would allow us to publish the connector for the same service.

[troystaylor]

Hello @BitcotDev @troystaylor, I will wait and watch your conversation before approving this connector, as I saw that two PRs are closed and open this PR.
@BitcotDev - Kindly finalize and let me know to proceed further, as @troystaylor mentioned Airtable connector is already present, please add your additional actions and triggers instead of creating new connector.

Hello Team, We want to publish the connector by our name. Please let us know what we need to do in this case.

You are welcome to contribute to the existing connector, but you cannot publish a new connector for the same service. Please refer to both of these pages: https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip#prepare-and-submit-your-connector-for-certification https://github.com/microsoft/PowerPlatformConnectors/wiki/Independent-Publisher-Connector-Group-%22Manifesto%22

Please let us know if using entirely different triggers and actions not currently employed by any existing connector would allow us to publish the connector for the same service.

I reviewed your artifacts again and noticed that you are trying to publish this connector as a business rather than as a personal community contribution. If that is the case, the Independent Publishers program is probably not for you, and you will want to submit the connector as a certified connector:
https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission
I understand that you developed this connector before submitting the proposal and apologize that we didn't catch this beforehand, but in the spirit of open source we cannot allow duplicate connectors and encourage contributing to existing connectors, which would enable you as a co-publisher.