Create custom connector TrueDialog #1337

TrueDialogDynamics · 2021-12-17T18:10:11Z

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.

ghost · 2021-12-17T18:10:23Z

All CLA requirements met.

certified-connectors/TrueDialog SMS/apiDefinition.swagger.json

sriyen-msft · 2022-01-11T01:40:02Z

certified-connectors/TrueDialog SMS/apiDefinition.swagger.json

+      "post": {
+        "responses": {
+          "201": {
+            "description": "Incoming messages callback created"


@TrueDialogDynamics Can you please let us know if this post action has schema definition?

@sriyen-msft Added schema for all the responses in this commit

sriyen-msft · 2022-01-11T01:40:41Z

certified-connectors/TrueDialog SMS/apiDefinition.swagger.json

+      "put": {
+        "responses": {
+          "201": {
+            "description": "Keyword callback created"


@TrueDialogDynamics Empty response schema is not allowed anymore, which means no dynamic content will be shown in the output and makers have to use parse JSON to parse the response. Please provide a valid response schema definition for all the operations in the swagger.

Added schema for all the responses in this commit

sriyen-msft · 2022-01-11T01:41:06Z

certified-connectors/TrueDialog SMS/apiDefinition.swagger.json

+      "put": {
+        "responses": {
+          "201": {
+            "description": "Stop callback created"


@TrueDialogDynamics Empty response schema is not allowed anymore, which means no dynamic content will be shown in the output and makers have to use parse JSON to parse the response. Please provide a valid response schema definition for all the operations in the swagger.

Added schema for all the responses in this commit

sriyen-msft · 2022-01-11T01:41:38Z

certified-connectors/TrueDialog SMS/apiDefinition.swagger.json

+            },
+            "CallbackToken": {
+              "type": "string",
+              "description": "CallbackToken"


@TrueDialogDynamics All the description values of properties are expected to be free from grammatical and spell errors. Please provide valid description values.
Docs - Define operation and parameter summaries and descriptions

Fixed descriptions in this commit

sriyen-msft · 2022-01-11T01:41:57Z

certified-connectors/TrueDialog SMS/apiDefinition.swagger.json

+      "put": {
+        "responses": {
+          "201": {
+            "description": "Delivery Notice callback created"


@TrueDialogDynamics Empty response schema is not allowed anymore, which means no dynamic content will be shown in the output and makers have to use parse JSON to parse the response. Please provide a valid response schema definition for all the operations in the swagger.

Added schema for all the responses in this commit

sriyen-msft · 2022-01-11T01:42:09Z

certified-connectors/TrueDialog SMS/apiDefinition.swagger.json

+      "put": {
+        "responses": {
+          "201": {
+            "description": "Invalid Targets callback created"


@TrueDialogDynamics Empty response schema is not allowed anymore, which means no dynamic content will be shown in the output and makers have to use parse JSON to parse the response. Please provide a valid response schema definition for all the operations in the swagger.

Added schema for all the responses in this commit

certified-connectors/TrueDialog SMS/apiDefinition.swagger.json

certified-connectors/TrueDialog SMS/apiProperties.json

sriyen-msft · 2022-01-11T01:44:39Z

certified-connectors/TrueDialog SMS/readme.md

+TrueDialog's SMS API is enterprise-grade with more pre-built features than any other SMS software. Built for developers and hosted in the Microsoft Azure cloud, our SMS API is highly reliable, secure and includes a pre-built ISO 9001 database for extra opt-out and compliance protection. Also available through our full-featured Enterprise-Grade SMS Texting Software.
+
+[Learn more](https://www.truedialog.com/sms-api-texting-api/) about what sets TrueDialog’s API apart from the rest.
+


@TrueDialogDynamics Please go thru the template provided for readme.md and add any required sections you are missing.

Updated readme file according to the provided template in this commit

Make changes according to the template file

natalie-pienkowska · 2022-01-21T16:00:13Z

Hi @TrueDialogDynamics! Our certification engineer, Srikanth, is currently on emergency leave. Please expect a delay with your PR. He will return January 31st, 2022. We apologize for any inconveniences.

sriyen-msft · 2022-02-08T01:16:30Z

@TrueDialogDynamics Sorry for the delay in response, Your connector pull request is approved and merged, you can submit your connector artifacts to the Connector certification tab in ISV Studio to move forward in the certification process, Thanks.

* Initial upload * Fix iconBrandColor * Update readme.md * Add stackOwner to apiProperties.json * Fix empty titles * Add schema definition for callbacks * Update description values of properties * Update readme.md Make changes according to the template file Co-authored-by: apoplutin <apoplutin@foundationmedicine.com>

apoplutin and others added 3 commits December 17, 2021 19:09

Initial upload

9999290

Merge branch 'microsoft:dev' into dev

eecc404

Fix iconBrandColor

1f46c03

TrueDialogDynamics requested a review from a team as a code owner December 17, 2021 18:10

Update readme.md

2298371

natalie-pienkowska added the certified-connector label Dec 27, 2021

sriyen-msft requested changes Jan 11, 2022

View reviewed changes

sriyen-msft added needs:partner-attention Validation phase Connector is being validated by Microsoft. labels Jan 11, 2022

apoplutin added 5 commits January 12, 2022 20:33

Add stackOwner to apiProperties.json

b78321b

Fix empty titles

25796ca

Add schema definition for callbacks

d4d6d4c

Update description values of properties

11f2fa8

Update readme.md

3ab5807

Make changes according to the template file

TrueDialogDynamics requested a review from sriyen-msft January 17, 2022 19:30

sriyen-msft approved these changes Feb 8, 2022

View reviewed changes

sriyen-msft merged commit a3e103e into microsoft:dev Feb 8, 2022

sriyen-msft removed Validation phase Connector is being validated by Microsoft. needs:partner-attention labels Feb 8, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Create custom connector TrueDialog #1337

Create custom connector TrueDialog #1337

TrueDialogDynamics commented Dec 17, 2021 •

edited

Loading

ghost commented Dec 17, 2021 •

edited by ghost

Loading

sriyen-msft Jan 11, 2022

TrueDialogDynamics Jan 14, 2022

sriyen-msft Jan 11, 2022

TrueDialogDynamics Jan 14, 2022

sriyen-msft Jan 11, 2022

TrueDialogDynamics Jan 14, 2022

sriyen-msft Jan 11, 2022

TrueDialogDynamics Jan 14, 2022

sriyen-msft Jan 11, 2022

TrueDialogDynamics Jan 14, 2022

sriyen-msft Jan 11, 2022

TrueDialogDynamics Jan 14, 2022 •

edited

Loading

sriyen-msft Jan 11, 2022

TrueDialogDynamics Jan 14, 2022

natalie-pienkowska commented Jan 21, 2022

sriyen-msft commented Feb 8, 2022

		TrueDialog's SMS API is enterprise-grade with more pre-built features than any other SMS software. Built for developers and hosted in the Microsoft Azure cloud, our SMS API is highly reliable, secure and includes a pre-built ISO 9001 database for extra opt-out and compliance protection. Also available through our full-featured Enterprise-Grade SMS Texting Software.

		[Learn more](https://www.truedialog.com/sms-api-texting-api/) about what sets TrueDialog’s API apart from the rest.

Create custom connector TrueDialog #1337

Create custom connector TrueDialog #1337

Conversation

TrueDialogDynamics commented Dec 17, 2021 • edited Loading

ghost commented Dec 17, 2021 • edited by ghost Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

TrueDialogDynamics Jan 14, 2022 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

natalie-pienkowska commented Jan 21, 2022

sriyen-msft commented Feb 8, 2022

TrueDialogDynamics commented Dec 17, 2021 •

edited

Loading

ghost commented Dec 17, 2021 •

edited by ghost

Loading

TrueDialogDynamics Jan 14, 2022 •

edited

Loading