How to get help

  • Different platforms are available to support developers depending on the type of help needed.

  • Community forums and Stack Overflow are resources for questions and advice, while the Issue Tracker is for product feedback.

  • Google Workspace administrators have access to email support for developer issues.

  • Check the Service status dashboard for known outages in Apps Script services.

Review the following options to find the best way to get developer support for Google Workspace APIs and tools.

You can also check the Service status dashboard to see if there are known outages in Apps Script services, and whether reported outages have been resolved.

Questions & advice

We use the popular programming Q&A website Stack Overflow to field technical questions. Google doesn't own or manage this site, but you can sign in with your Google Account.

Developers use the tag [google-apps-script] to mark questions relevant to this service. You can search existing questions or ask a new question:

Ask a new question

As an alternative to StackOverflow, you can also get advice from the Reddit Apps Script community .

Refer to the Google Workspace developer community page for additional resources, discussion forums, and chat channels.

Developer product feedback

If you have feedback about developer product features or functionality, search our Issue Tracker to see if others have already submitted the same feedback. If you find an existing feedback report, click the star next to the issue number to express your agreement and help us prioritize it.

If no one else has submitted similar feedback, you can submit a new feedback report.

Submit bug Submit feature request

Contact Google Workspace support

If you are a Google Workspace customer, your administrator can email a Google Workspace developer support specialist for direct assistance.

Make sure you include the following information when you contact us:

  • A description of the problem, and the behavior you expected instead.
  • A list of steps and a small snippet of sample code that can be used to reproduce the problem.
  • A description of the output you expect and what actually occurred. Include any error messages you receive.
  • Information about your development environment, including programming language, library versions, etc.