Skip to content

Conversation

@krautrocker
Copy link
Contributor

  • Includes certification zip file

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.

- Includes certification zip file
@krautrocker krautrocker requested a review from a team as a code owner September 21, 2025 17:54
@krautrocker
Copy link
Contributor Author

ConnectorPackage validation:

image

@krautrocker
Copy link
Contributor Author

Proof-of-life:

Get all surveys:

image

Get Single Series Data:

image

Get Popular Series:

image

@krautrocker
Copy link
Contributor Author

krautrocker commented Sep 21, 2025

One action for this connector - get multiple surveys - may work similarly to World Bank. Swagger bombs out in a flow so I went schemaless in YAML (object + additionalProperties: true) and handle the parsing downstream for that action.

Working out a C# option that normalizes the payload in a fixed, predictable shape for a flow...but getting this error when trying to use custom code:

Failed to provision compute for custom code. Request failed with error 'Code: BadRequest. Message: <!DOCTYPE html> <html> <head> <title>There is not enough space on the disk.<br></title> <meta name="viewport" content="width=device-width" />

Just have to wait until the container clears, I assume, so going schemaless for now. I wanted to get this up here before the next round of BLS data comes out. See here: https://www.bls.gov/schedule/2025/09_sched.htm

@vmanoharas
Copy link
Contributor

Hi @krautrocker,

Our IP connector certification process has been changed. Kindly refer the below link. As per the process, we have shared a MS Form through email to the email that you mentioned in the swagger file. Please fill the form to proceed for the next process and please reply here once the form is filled.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip#step-5-onevet-verification

@krautrocker
Copy link
Contributor Author

Just submitted the form @vmanoharas

@vmanoharas
Copy link
Contributor

Hi @krautrocker,

We have sent onevet verification link. Please complete the verification process.

@krautrocker
Copy link
Contributor Author

I just resubmitted the form but I'll keep a look-out for another request.

@krautrocker
Copy link
Contributor Author

OneVet verification complete based on previous data, as discussed. Will re-verify once every three months @vmanoharas

@vmanoharas
Copy link
Contributor

certify-connector

@certificationteam
Copy link
Collaborator

Congratulations — your certification request has been approved. Your connector will be included in the upcoming deployment schedule for production release and the supporting documentation will be published. This end-to-end process typically takes 3–4 weeks.

Many Thanks,
Copilot Connector Certification Team

@krautrocker krautrocker changed the title Proposal - Bureau of Labor Statistics (Independent Publisher) Bureau of Labor Statistics (Independent Publisher) Oct 14, 2025
@krautrocker
Copy link
Contributor Author

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants