> For the complete documentation index, see [llms.txt](https://docs.workflowgen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.workflowgen.com/integration/8.7/undefined.md).

# WorkflowGen Integration Guide

This guide provides instructions on:

* How to use the WorkflowGen GraphQL API.
* How to use the WorkflowGen web services API.
* How to create incoming and outgoing webhooks.
* How to build applications for WorkflowGen using .NET Framework. .NET developers can use the WorkflowGen.My assembly to manipulate the WorkflowGen context, and non-.NET developers can work with the WorkflowGen context without using the WorkflowGen.My assembly.
* How to use WorkflowGen.My to develop a RemoteLaunch SDK application to launch a process from outside the WorkflowGen environment.
* How to use an OAuth 2.0 access token for server-side .NET development.
* How to create custom authentication modules.
* User management and directory synchronization.
* How to customize the WorkflowGen User Portal.
* How to create integrations using WorkflowGen URLs to perform certain process functions.
* How to set up and customize notifications.

It also contains a table that lists time zone names and IDs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.workflowgen.com/integration/8.7/undefined.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.