Troubleshooting JSON Parser Errors: Collection to Text Conversion

Welcome to the callin.io community!

1. Screenshots of module fields and filters

Please share screenshots of the relevant module fields and filters in question. It would greatly assist other community members in understanding your situation.

You can upload images here using the Upload icon in the text editor:

2. Scenario blueprint

Please export the scenario blueprint file to enable others to review the mappings and settings. You can find the Export Blueprint menu item at the bottom of the scenario editor by clicking on the three dots.

^{(Note: Exporting your scenario will not include private information or connection keys)}

Uploading it here will appear as follows:

blueprint.json (12.3 KB)

3. And most importantly, Output bundles

Please provide the output bundles of the TRIGGER module [1] by running the scenario (or retrieve them from the scenario History tab). Then, click the white speech bubble on the top-right of each module and select “Download input/output bundles”.

A.

Save each bundle's content in your text editor as a bundle.txt file and upload it to this discussion thread.

Uploading them here will look like this:

module-1-output-bundle.txt (12.3 KB)

B.

If you are unable to upload files on this forum, you can alternatively paste the formatted bundles in this manner:

• Either add three backticks ``` before and after the code, like this:

  ```
  <sup>input/output bundle content goes here</sup>
  ```

• Or use the format code button in the editor:
  

Providing the input/output bundles will enable others to replicate what is happening in the scenario, even if they do not use the external service.

Following these steps will allow others to assist you. Thanks!

The Parse JSON module expects a text string containing properly formatted JSON and then creates the necessary bundles, composed of arrays and collections, from the original text string.

You appear to have a callin.io trigger, which will generate already parsed output bundles ready for use by other modules. Consequently, you won't have any JSON coming out of callin.io (unless, of course, one of the elements itself is a JSON string). Based on your screenshot, it doesn't seem like callin.io is sending out any JSON strings, so you likely don't need the Parse JSON module there.

If you can show us the output bundle from the callin.io trigger, we can help you identify what to map into your MySQL module for searching. Most likely, you can map the value directly into the MySQL module, but it all depends on what you need to retrieve from the callin.io trigger.

–
Director of NewPath Consulting - we are

!