Form Director Newsletter for the month of July

Newsletter for the month of July 2025

Form Director updates

Form Director Story:

📌 From Forms to Flow: The Form Director Story

Google Forms made it easy to collect data.
But what happens after someone hits "Submit"?
📉 Manual work
🕒 Lost time
📂 Disconnected systems

💡 That’s where Form Director comes in.

Born from the need to turn form submissions into seamless workflows, Form Director connects Google Forms to your favorite apps — Google Sheets, Docs, Calendar, Gmail, Tasks, Trello, Slack, HubSpot, Zoho, and more.

✅ Create calendar invites
✅ Auto-generate Google Docs
✅ Send personalized emails
✅ Add CRM leads automatically
✅ Trigger task creation

All without a single line of code.

✨ Turn forms from a dead-end into a powerful launchpad for action.
Welcome to a world where your forms flow.

Note: Transform your business and achieve breakthrough results with our expert Professional Services, designed to help you harness the power of intelligent integration and hyper-automation.

The User of the Month - July 2025

Congratulations Masrhiem Taufik for being selected as the user of the month of July for Form Director.

This is what they feel about Form Director:

"This is a great tool to use. I can eliminate the use of paper for my whole organization. Decisions are made faster and saves a lot of time. There is some learning to do on how to operate but once you get the hang of it, it is a breeze. Best of all are the staff who responses back to me the same day whenever I have an issue. They were able to solve each problem and even organized an online meeting to go through my mistakes step by step. Fantastic customer service!"

The user of the month will be displayed on the spotlight page of our community website. Please check the spotlight page for more details.

Challenges and Solutions

Challenges faced 81581

Nick (name changed), a Form Director user, reached out with the following question:

All of a sudden I am unable to process my forms. I am receiving the following error....

{
  "message": "Request failed with status code 401",
  "name": "AxiosError",
  "stack": "AxiosError: Request failed with status code 401\n    at settle (file:///workspace/node_modules/axios/lib/core/settle.js:19:12)\n    at Unzip.handleStreamEnd (file:///workspace/node_modules/axios/lib/adapters/http.js:599:11)\n    at Unzip.emit (node:events:530:35)\n    at Unzip.emit (node:domain:552:15)\n    at endReadableNT (node:internal/streams/readable:1698:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)\n    at Axios.request (file:///workspace/node_modules/axios/lib/core/Axios.js:45:41)\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async executor.execute (file:///workspace/server/executor.js:19:5)\n    at async file:///workspace/server/approval.js:47:28",
  "config": {
    "transitional": {
      "silentJSONParsing": true,
      "forcedJSONParsing": true,
      "clarifyTimeoutError": false
    },
    "adapter": [
      "xhr",
      "http",
      "fetch"
    ],
    "transformRequest": [
      null
    ],
    "transformResponse": [
      null
    ],
    "timeout": 0,
    "xsrfCookieName": "XSRF-TOKEN",
    "xsrfHeaderName": "X-XSRF-TOKEN",
    "maxContentLength": -1,
    "maxBodyLength": -1,
    "env": {},
    "headers": {
      "Accept": "application/json, text/plain, */*",
      "Content-Type": "application/json",
      "ContentType": "application/json",
      "Authorization": "Bearer ya29.a0AS3H6Nxe0cCwBYANPxjnvXBzfJ3DHLjaFjfntcoaTz9D4E_P8INrM-iNaMkcDAAnuUT6sqNkxLsnjIbN9goUrCJDo22b3zdDu7NLYTplJxXPXHL1eWWrDnMrhXCEfXNFq_KlZ2fhwL_hfE5RklkcaTsyzG3wu5kLfvjNK6NiQNgaCgYKAW0SARcSFQHGX2MipSlv4-jRiNIsVAYDyr9uog0178",
      "Access-Control-Allow-Origin": "*",
      "Access-Control-Allow-Headers": "Origin, X-Requested-With, Content-Type, Accept",
      "User-Agent": "axios/1.8.4",
      "Content-Length": "606",
      "Accept-Encoding": "gzip, compress, deflate, br"
    },
    "method": "post",
    "data": "{\"function\":\"onApprovalAction\",\"parameters\":{\"formId\":\"1c2OKDgi9XYEcGHgBmkUBqG71xYSeud23V46HLxHxMiQ\",\"email\":\"jr.rogers@audacy.com\",\"responseId\":\"2_ABaOnuewrAMlwWO2aR7q6IE9ZWZZhXuhBn4uzzb-4vWL35WKa9PZhqt1iF8IVLmFgC-tsIU\",\"serviceId\":\"SERVICE_1661201993692\",\"requestorEmail\":\"\",\"status\":\"Approved\",\"comment\":\"\",\"attachments\":\"{}\",\"level\":\"service\",\"responseAutoIncrement\":\"208\",\"signatureRequired\":false,\"attachToServiceOutput\":false,\"approvalLevelIndex\":\"0\",\"approvalIndex\":\"0\",\"updatedAt\":\"2025-07-24T19:08:12.660Z\",\"isExist\":false,\"recipientStatus\":[{\"jr.rogers@audacy.com\":\"Approved\"}]},\"devMode\":false}",
    "url": "https://script.googleapis.com/v1/scripts/AKfycbzSTV3pJ69CUTyT6QEclyK9n8mhBKGI01n6F3L4F0j0knAzudBI:run",
    "allowAbsoluteUrls": true
  },
  "code": "ERR_BAD_REQUEST",
  "status": 401
}

Any guidance you might be able to give would be much appreciated.

Proposed Solution

For Nick's question, We’ve recently made an update to the Form Director add-on to enhance its email-sending capability by introducing support for GmailApp, as recommended by Google's official documentation.

As part of this enhancement, we have added a new Gmail-related scope required by the library. Due to this change, Form Director may prompt you to reauthorize access the next time you use the add-on.

No worries—this is a simple one-time step:

Open the Form Director add-on from your Google Form.
When prompted, click to authorize the requested permissions.
Once authorized, proceed as usual—your setup will continue to work as expected.

If you have configured the approval flow, you also need to authorize the approval service. To do this, open the add-on → Approval section → Reauthorize. For more details, check our guide here .