Debugging 101: Solving Common Errors in the FlowGear Integration Tool

By Karan Shetye 02-Feb-2023


Flowgear is a cloud-based integration platform that allows businesses to streamline their processes by connecting various applications and data sources. This tool provides a powerful and flexible way to automate tasks and workflows, eliminating the need for manual intervention and reducing the risk of errors.
With Flowgear, you can integrate your favorite apps and systems, from enterprise resource planning (ERP) and customer relationship management (CRM) systems to cloud storage and communication tools. Whether you’re looking to simplify your supply chain management, boost your sales and marketing efforts, or streamline your internal processes Flowgear can help you achieve your goals and drive business success.

Popular Integration with Flowgear:

  • Salesforce
  • Microsoft Dynamics
  • Xero
  • QuickBooks
  • Zoho CRM
  • Shopify
  • Magento
  • Zapier
  • Google Drive
  • Slack

Above is the list of the top 10 popular tools which we can integrate using the FlowGear Integration tool. Flowgear enables companies of all sizes to increase efficiency and reduce costs by integrating their apps, services, API’s and databases. No coding with 200+ pre-built connectors, reusable workflows, and APIs.

Methods of Integration with Flowgear:

  • API integration
  • File-based integration
  • Database integration
  • Web services integration
  • Cloud-to-cloud integration
  • SaaS integration
  • B2B integration
  • Event-driven integration
  • ETL (extract, transform, load) integration
  • Workflow automation

And many more.
By using Flowgear’s integration methods, you can quickly and easily integrate your systems and automate the transfer of data between them. Flowgear provides a flexible and scalable platform that allows you to integrate your systems in a way that meets your specific requirements.

Step to connect Flowgear to your System:

1. Sign up for a Flowgear:
Go to the Flowgear website and sign up for a Flowgear account. You’ll need to provide some basic information, including your name and email address.

2.Add a new connection:
Once you’ve signed up for a Flowgear account, log in to the Flowgear portal and go to the “Connections” section. From there, click on “Add Connection” and select the type of system you want to connect to, such as Salesforce, a database, or an API.

3.Configure the connection:
Flowgear will provide a set of instructions for configuring the connection, including any credentials or API keys you’ll need to provide. Follow these instructions to configure the connection.

4.Test the connection:
Once you’ve configured the connection, you can test it to ensure it’s working correctly. Flowgear will usually provide a test feature that you can use to verify the connection.

5.Start using the connection:
If the connection is working correctly, you can start using it to automate your business processes. You can use Flowgear’s flow designer to build flows that automate the transfer of data between your systems, and you can use the monitoring and reporting features to track the performance of your flows.

Debugging 101:

1.) The workflow could not be updated!

This error mainly occurs when your Site is not registered with Flowgear. Mainly when you are a new user of Flowgear. If this error is not resolved then you cannot go ahead with the process.

Steps to be followed:

a.) Add Site
Click on Top Right Name Icon > Click on Add a new Site

Fill in your details. The example is shown above.

b.) DropPoint

Add a DropPoint by clicking on the New button.
One software will be getting downloaded to your system.

In the Search box type “Flowgear DropPoint” and click on Run as administrator.

NOTE: The use of DropPoint is that it allows you to get the data from your system.

Click on the Sign In button.

Now you can see in the above picture that the system is connected to the Flowgear.

Now you can see our workflow is successfully running.

2.) Unable to run Workflow: JSON Convert: Data at the root level is invalid.

This error usually occurs when we connect two nodes wrongly.

NOTE: Flat File Node is used to convert an XML document to a flat file, or a flat file to an XML document.

Here we are converting Flat File to an XML file. When we connect File Node’s Content to Flat File Node’s FlatFileDocument the File gets converted to an XML file.
But in the next step, we are trying to connect Flat File Node’s FlatFileDocument to the JSON Convert XML which throws an error.
Below is the solution.

Here we should try to connect Flat File XMLDocument to the JSON Convert XML.

3.) Web Request: The remote server returned an error (404) Not Found.

404 error codes are generated when a user attempts to access a webpage that does not exist, has been moved, or has a dead or broken link.

We just removed the “number” from the URL and then:

4.) Web Request: The remote server returned an error (404) Not Found.

As we mentioned why error 404 occurs in the 3rd point.
Here the error occurs because of id = 999 which is out of the limit or the website is having insufficient data to generate the value for id = 999.

Here we have given an id = 24 which is the last id number for the values present in the website data.

5.) Unable to run Workflow: File: DropPoint Invoke Error while invoking Node: Illegal characters in path.

If you read the above error carefully it says “Illegal characters in path” which tell us that the Path present in the File has Illegal characters. This usually happens when we copy the path of the file from our system and paste it into the File node.
Below is the right way to write the path in the node.

6.) Unable to run Workflow: File: Please specify a connection for the File node.

The above error specifies the connection of the File Node.
In the above workflow, we are using two File nodes so the error will be in either of the nodes. If you see the second File Node, Connection is missing.

NOTE: While using File Node mentioning the connection is mandatory.

7.) Unable to run Workflow: Microsoft SQL Table Update: String or binary data would be truncated. The statement has been terminated.
The procedure is attempting to store something in the Microsoft SQL table that is larger than the column allows. In our case is the name of the company(company_name).

Below is the overview of the QuickMap node.

Here we have added the LEFT({company_name}, 15) which is going to trim the characters. REPLACE({phone},”-“, “.”) and REPLACE({phone1},”-“, “.”) are going to replace “ – ” with “ . ”.

About the Author