On this page:

Why am I receiving an email with the title Doc Action failure for <form/workflow name>?

If the submission doesn't reach the Google Connector, all tenant administrators or workflow admins (if configured)  will receive a Doc Post Failure notification email reporting information about the error. Note the email subject contains the server name where the form/workflow is hosted.

Here are some examples:

Why won't the Doc Action wizards connect forms/workflows to my Google Account ?

Google users with 100+ pre-existing documents in their Google Drive may have issues using the frevvo Doc Action Wizards to connect forms/workflow to their Google account. The login screen in the wizard may hang or throw an unexpected error. If you experience this issue please:

1. Update to the supported version of frevvo Google Connector.
2. Note: If you are using Live Forms Online, cloud hosted software the frevvo Google Connector is already updated.
3. Use the form/workflow Manually Set Doc URIs wizard and do NOT use the frevvo Google Sheet wizard

In the form/workflow Manually Set Doc URI, do the following:

• in the Write method, put the URL to the frevvo Google Connector and set the key in the URL to your Google Sheet, username and password. For example:

https://app.frevvo.com:443/google/spreadsheets/key/1ytf4_eeN7b77321BxLsZfOeg6oWlgAnqI4OglDFASGg/w/Sheet1?user=joe%40gmail.com&password=mypassword

The big ID after the key/ comes from the Google Spreadsheet URL that you see in the browser. It looks like this: https://docs.google.com/a/frevvo.com/spreadsheets/d/1ytf4_eeN7b77321BxLsZfOeg6oWlgAnqI4OglDFASGg/edit#gid=0

The parameters indicated in the URL: ?user=xxx&password=yyy. You should URL encode the user and password though this may not be required e.g. joe@gmail.com will work fine. You don't need to URL encode the @. Some characters must be encoded e.g. &. Spaces in the Google Sheet and worksheet names should be encoded with the + (plus) sign. For example, a worksheet named Employee Information should be encoded as Employee+Information. 

If you aren't sure, encode it (http://meyerweb.com/eric/tools/dencoder/).

This workaround bypasses the wizard completely and points the form to the Connector directly via a manual doc URI.

"Invalid Credentials" message.

When logging in to the 'Save to Google Docs' or Save to Google spreadsheet wizards using a gmail address like, someone@gmail.com, you may see the message "Invalid Credentials". Gmail prevents logins from new locations and marks them as suspicious. Follow these steps to enable login from the unknown device:  

• Navigate to https://security.google.com/settings/security/activity?pli=1. 
• If you are a cloud customer, select ‘YES, THAT WAS ME’ for the unknown device with IP address 54.86.85.105 - this is the ip address of the frevvo SaaS server.
  
  
• In-house customers may see the ip address of their own server.

How do I find the version of the Google connector?

"Unknown Error has Occurred" message when logging on to the Save to Google Spreadsheet wizard

In-house customers:

 in-house customers may encounter an "Unknown Error has Occurred" error when logging on to the Save to Google Spreadsheet wizard. If you see "Error creating bean with name 'credentialController" in the <frevvo-home>/tomcat/logs/frevvo.log file, then the error was caused by starting  without the client_secrets.json file present in the <frevvo-home>/tomcat/lib folder. Follow these steps to resolve the issue:

1. Stop .
2. Navigate to the Credentials screen for the project you created for your Google Account at https://console.developers.google.com. 
3. Click the Download JSON file.
   1. Rename JSON file as client_secrets.json
   2. Copy it to tomcat/lib folder.
4. Restart .

Cloud and in-house customers:

Cloud and in-house customers may see this error when selecting a Google sheet from the dropdown after you log into the wizard with your Google account and access code. To prevent this, set the Share permission for your Google Sheet to private then run the Save to Google Spreadsheet wizard. Change the share permission to public once the wizard is completed.

There are other causes for this error. Contact  support if this solution does not solve your problem.

"Syntax Error: missing ; before statement" error

You may see the error: "Syntax Error: missing ; before statement" followed by the name of your form/workflow and the name of the rule containing the error in the debug console when testing a form/workflow that reads or updates a Google sheet via the Google Connector.

This may be because you are using an invalid or revoked access token in your business rule. Make sure you are using a valid access token and retest.

Internal Server Error

You may encounter this error when performing read/update/write operations to a Google sheet from a form/workflow. The Google API can never be a replacement for a database in terms of reliability. There are no SLAs associated with free google accounts. makes multiple http calls to the Google API with no guaranteed SLA.  As the load increases, the chances that the Google service might fail increases. If you encounter the 'internal server error', the only thing to do is to try again later

Google Connector Known Issues

Please report any issues or feedback to us here. See the list below for some known issues with the Google Connector.