Add Text Request connector files

[connorjustbecause]

---

Text Request Connector

• [X] 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.
• [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.
• [X] 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.

We are not an Independent Publisher

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

[ghost]

All CLA requirements met.

[v-EgorKozhadei]

Hello @connorjustbecause,

Thank you very much and congratulations on your new submission. Our Certification Engineers will review it within 1-2 weeks.

Please let us know if you have any questions.

Thank you very much again for working with us.

[connorjustbecause]

Thanks @v-EgorKozhadei,

I would like to ask a question about the default values that have been flagged as look-a-like-values. I am afraid any guid example would be a look-a-like-value, even if the guid example was 00000000-0000-0000-0000-000000000000.

Would a basic description in place of the description work? Something like

"contact_tags": [ "<Enter guid here>",

Or would it be better for there to be no default at all?

This question applies to URL default values as well. Should there be a placeholder, or just no url at all?

[v-EgorKozhadei]

Thanks @v-EgorKozhadei,

I would like to ask a question about the default values that have been flagged as look-a-like-values. I am afraid any guid example would be a look-a-like-value, even if the guid example was 00000000-0000-0000-0000-000000000000.

Would a basic description in place of the description work? Something like

"contact_tags": [ "",

Or would it be better for there to be no default at all?

This question applies to URL default values as well. Should there be a placeholder, or just no url at all?

Hello @connorjustbecause,

Thank you for your question!

Unfortunately, all secret-look-a-like-values need to be replaced with string value or removed, even example GUIDs that consist of zeros. A basic description instead of secret-look-a-like-value would be fine. If you don't want to change it to a description, you can remove the value.

Please let us know if you have any questions.

[v-EgorKozhadei]

Hello @connorjustbecause,

I hope you are doing well.

Congratulations, your pull request is approved and merged. Please submit the files to ISV Studio or update your submission using your latest commit ID, please allow us up to 1-2 weeks to review your submission, and our Engineers will notify you in the “Activity Control” area in ISV Studio. Please make sure that the icon meets all the requirements, that it’s size is 230x230, icon background is not white or transparent and it matches the iconBrandColor property in apiProperties.json file.

After making the submission in ISV Studio, please attach an intro.md file in the activity control section. This file is required and it's different from readme.md. You can find an example of intro.md file on this page at step 6.

Please Create an environment in the Preview region. You will use this environment later to test your connector after Microsoft is done with the functional verification for your connector.

We expect all tests to be completed within 1-2 weeks.

If your connector passes all tests, the deployment process begins, and it typically takes up to 3 to 4 weeks to deploy your connector to all of our regions.

Please let me know if you have any questions.

Thank you very much for working with us.