> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.edworking.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Integrations, API & Webhooks in Edworking


Edworking offers multiple ways to connect its all‑in‑one workspace to other applications. You can build custom integrations using Edworking’s **GraphQL API**, or automate workflows without code using **Zapier** and **Pabbly Connect**. This guide explains what’s available and how to start.
## 1. Overview of integration options
* **No‑code integrations through Zapier & Pabbly Connect –** Edworking integrates with thousands of apps via Zapier and Pabbly Connect. These tools let you automate tasks (e.g., create a task when a new email arrives), keep data in sync across tools, and build workflows without writing code. The integration page notes that Edworking can “seamlessly integrate with thousands of applications through Zapier and Pabbly Connect” and that you can automate workflows, sync data in real time and set up integrations without [code](https://edworking.com/integrations#:~:text=Connect%20Edworking%20with%20Your%20Favorite,Tools).
* **GraphQL API –** For developers who need custom functionality, Edworking exposes a GraphQL API. You can explore the API documentation and run queries against their public endpoint. The API docs encourage users to “build your own custom integrations and Edworking apps” and to explore what’s possible via the [reference section](https://edworking.com/api/overview/get-started#:~:text=Edworking%20API%201).
* **Webhooks –** Edworking does not currently expose standalone webhook endpoints. However, you can achieve webhook‑like functionality by using Zapier or Pabbly Connect. For example, in a Zapier workflow you can add a “Webhooks by Zapier” action to send Edworking data to another system whenever a trigger event occurs.
## 2. Getting your Edworking API token
All API requests require an access token in the **Authorization** header. Edworking supports OAuth for third‑party apps, but the simplest way to get started is to use your personal token. According to the API docs, any Edworking user can generate a [personal token](https://edworking.com/api/overview/authentication#:~:text=All%20Edworking%20API%20queries%20require,a%20valid%20Edworking%20access%20token):
1. **Log into Edworking** and open your workspace.
2. Click your **avatar** in the top‑right corner and choose **Preferences** from the dropdown menu.
3. In the **Profile** screen, choose **My Account**. Under the **API Token** field, click **Copy Token**. This copies the personal token to your [clipboard](https://edworking.com/api/overview/authentication#:~:text=Any%20Edworking%20user%20can%20generate,a%20personal%20token).
Below is a screenshot of the **My Account** page showing the API token field and **Copy Token** button:

> **Privacy tip:** Treat your API token like a password. Store it securely and do not expose it in client‑side code or public repositories.
## 3. Using the Edworking GraphQL API
The API endpoint is a GraphQL server located at `https://gateway.edworking.com/` (a demo server is also available). You send POST requests containing a GraphQL query or mutation and include your token in the `Authorization: Bearer <YOUR_TOKEN>` header. Here’s a simple cURL example to list projects:
```
curl -X POST \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{"query": "{ getProjects { id name } }"}' \
  https://gateway.edworking.com/

```
### 3.1 Categories of queries & mutations
Edworking’s API exposes numerous queries and mutations for different parts of the platform. Below is a non‑exhaustive overview. Use the API docs to see all available fields and [parameters](https://edworking.com/api/overview/get-started#:~:text=Edworking%20API%201).
| Category | Query examples | Mutation examples |
| ---- |
| **Tasks & projects** | `getTasks`, `getProjects`, `getProjectBasic` | `setTask` (create/update task), `setProject` |
| **Files & folders** | `getFiles`, `getFolders` | `setFile`, `setFolder`, `delFile`, `delFolder` |
| **Chat & messages** | `getChat`, `getMessages`, `getMessagesStates` | `setMessage` |
| **Billing & users** | `getBilling`, `getInvoices`, `getUserBasic`, `getUsers` | `inviteUser`, `inviteUserEmail` |
| **Statistics & analytics** | `getStats`, `getStories`, `getStatesProject` | `createState`, `updateState`, `duplicateTask` |
**Exploring the API:** The documentation at `https://edworking.com/api` lets you view each query/mutation, its arguments and return type. It also includes a GraphiQL playground so you can test queries against your own workspace.
## 4. Setting up integrations with Zapier
Zapier provides a user‑friendly way to integrate Edworking with thousands of other apps. Here’s how to get started:
1. **Sign up or log in to Zapier.**
2. **Create a new Zap** and search for **Edworking** in the trigger step. Choose a trigger event (e.g., “New Task Created” or “New Message”).
3. **Connect your Edworking account.** When prompted, Zapier will ask for your Edworking API token. Paste the token you copied from the **My Account** page. Zapier uses this token to access your workspace.
4. **Define an action** in another app (e.g., create a task in Trello, send an email via Gmail, call a webhook). Map data fields from Edworking to the destination app.
5. **Test and turn on** the Zap. From now on, each time the trigger event happens in Edworking, Zapier will run the action.
Because Zapier also offers a **Webhooks by Zapier** app, you can send Edworking data to any URL as a POST request, effectively creating custom webhooks.
## 5. Integrating with Pabbly Connect
Pabbly Connect is another no‑code integration platform supported by Edworking. It works similarly to Zapier but may offer more flexible pricing or features. To use Pabbly:
1. **Create a Pabbly Connect account.**
2. **Start a new workflow** and choose Edworking as either the trigger (event occurs in Edworking) or the action (perform an operation in Edworking). For example, choose “New Task” as the trigger.
3. **Connect your Edworking account** by providing your API token. Pabbly will authenticate with Edworking.
4. **Add additional steps**, such as filters, formatters or actions in other apps (e.g., Slack, Google Sheets). Pabbly also includes a **Webhook** action that can send HTTP requests to any endpoint when triggered.
5. **Save and activate** the workflow. Pabbly will handle sending data between Edworking and the other services automatically.
## 6. Tips and resources
* **Explore documentation:** Use the left sidebar of the API reference (`https://edworking.com/api`) to explore queries and mutations. Each page shows argument names and types and often includes example queries.
* **Limit permissions:** Only share your personal token with trusted services. If building a public app, implement the OAuth flow rather than sharing a [personal token](https://edworking.com/api/overview/authentication#:~:text=All%20Edworking%20API%20queries%20require,a%20valid%20Edworking%20access%20token).
* **No built‑in webhook events:** Because Edworking doesn’t currently provide first‑party webhooks, rely on integration platforms (Zapier, Pabbly) or the GraphQL API to build real‑time workflows.
* **Contact support:** For complex integrations or if you have questions, you can reach Edworking’s support team via the in‑app chat or email.
By using the GraphQL API for granular control or leveraging no‑code platforms for quick automation, you can seamlessly integrate Edworking with your existing tech stack and keep your work in sync across tools.