Download Mobile AppWhat should stay in Edworking?
Tasks, deadlines, docs, meeting notes, files, approvals, and decision follow-up should stay in Edworking so every connected signal has an owner and next step.
CatalogNative sync, automation, API and imports
Connect Edworking with the Tools your Team Already Uses
Sync calendars and development work, automate processes with Zapier or Pabbly, build custom workflows with the GraphQL API, or import projects from your current platform.
- Google Calendar and GitHub Native connections
- Zapier and Pabbly No-code automation
- GraphQL API Build your own
- Six import sources One-time migration
Free plan to get started. API, Zapier and Pabbly need the Business plan.
Four ways to connect
Pick the Connection Type that Matches your Work
Each type behaves differently. Native connections stay live, automations run per event, the API is yours to build on, and imports move data once.
Native sync
Continuous connections built directly into Edworking.
Google Calendar, GitHub
See native integrationsNo-code automation
Workflows that run through an automation platform on each event.
Zapier, Pabbly Connect
See triggers and actionsBuild with the API
Read, create and update workspace data programmatically.
GraphQL
See the API previewImport your work
One-time migration from your current project tool.
Asana, ClickUp, Jira, Monday, Notion, Trello
See import coverageNative integrations
Connections Built Directly into Edworking
You connect these once in your profile settings. They stay live without an automation platform in between.
Google Calendar
All plansConnect one or more Google accounts, choose which of their calendars appear inside Edworking, and turn on the Edworking Tasks calendar so deadlines show up alongside your meetings.
- Direction
- Both ways
- What it covers
- Calendars, events, task deadlines
- Set up in
- Profile settings, Integrations
| Behavior | Supported |
|---|---|
| View your selected Google calendars inside Edworking | Yes |
| Include Edworking task deadlines in your calendar view | Yes |
| Edit a Google Calendar event from inside Edworking | Not documented |
| Update an Edworking task by editing a Google Calendar event | Not documented |
Two rows are still being confirmed with engineering. Until they are published, plan around the two behaviors marked Yes.
Editing events across the two systems is not documented. Treat the connection as calendar visibility, not event management.
Connect Google CalendarLast verified: August 2026
Google CalendarChoose which calendars appear in Edworking
Connected account
SC
Sarah Chensarah.chen@gmail.com
Sarah Chensarah.chen@gmail.comAvailable calendars
2 of 4 calendars shown
GitHub
All plansInstall the Edworking GitHub App on the repositories you choose, then pull issues into a default space and keep pull-request status visible next to the task it belongs to.
- Direction
- Into Edworking
- What it covers
- Issues, pull-request status, tasks
- Set up in
- Profile settings, Integrations
What you can configure
- Install the Edworking GitHub App on selected repositories
- Sync pull-request status back to the linked task
- Link work automatically using an Edworking task ID
- Create Edworking tasks from GitHub issues
- Choose the default Edworking space for imported issues
- Reconfigure or disconnect the installation at any time
Work is linked through an Edworking task ID. Commit-level linking and GitHub notification delivery are not part of the documented installation.
Install the GitHub AppLast verified: August 2026
GitHubEdworking GitHub App installed on 3 repositories
Sync behavior
Default space for imported issues
Automation platforms
Run Workflows Through Zapier or Pabbly Connect
Both platforms connect Edworking to their own app catalogs, but their Edworking coverage is not the same. Zapier can start a workflow from Edworking. Pabbly currently only writes into it.
Zapier
BusinessZapier can start workflows from Edworking and run actions in your workspace. The operations below are examples; the official listing has the current catalog.
- Direction
- Both ways
- What it covers
- Projects, tasks, messages, files
- Set up in
- Zapier editor
| Operation | Type | Notes |
|---|---|---|
| New Message | Trigger | Fires on a new message in a task, space or private chat |
| New Project | Trigger | Triggers when a new project is available |
| New Task | Trigger | Triggers when a new task is available |
| Create Task | Action | Needs a space, title, description and project state |
| Send Message | Action | Needs message content and a chat destination |
| Upload File | Action | Uploads a file from a URL to a space or task |
Version 2.0.0 is being prepared with scoped tokens and the existing actions, triggers and task search. Version 1.4.0 uses account sign-in. When 2.0.0 is available, reconnect with an API token, verify field mappings and test each Zap. Select read permissions for dropdowns and files:read for message attachments. Replace expiring tokens and reconnect before expiry. Your Zapier plan determines polling frequency.
Open the Zapier listingLast verified: October 2026
Pabbly Connect
BusinessPabbly Connect can write into Edworking with four actions. It publishes no Edworking triggers, so a Pabbly workflow has to start somewhere else.
- Direction
- Into Edworking only
- What it covers
- Projects, tasks, messages
- Set up in
- Pabbly Connect workflow
| Operation | Type | Notes |
|---|---|---|
| Create Task | Action | Creates a task in an Edworking space |
| Create Project | Action | Creates a new space or project |
| Create New Message | Action | Posts a message into a chat |
| Get Private ID | Action | Returns a private chat ID for use later in the workflow |
No Edworking triggers are available. Check the connector authentication instructions before connecting; a scoped API token is not a drop-in replacement for a session credential.
Open the Pabbly listingLast verified: August 2026
Verified workflows you can copy
Each one opens the partner page where the trigger and action are published.
Google Calendar event created or updatedCreate an Edworking taskOpen templateNew GitHub issueCreate an Edworking taskOpen templateNew Google Forms responseCreate an Edworking taskOpen templateNew Edworking messagePost it to a Slack channelOpen templateNew Edworking messageAdd a row in Google SheetsOpen templateNew Gmail emailCreate an Edworking taskOpen template
Developer API
One GraphQL Endpoint for Workspace Workflows
Build workflows with scoped API tokens for tasks, messages, projects and files. Choose the permissions each integration needs.
- Endpoint
- https://gateway.edworking.com/
- Authentication
- Scoped API token in the Authorization header
- Required plan
- Business
- Rate limits
- Not published
- Webhooks
- Not available. Poll the supported read operations.
- Last verified
- October 2026
Supported permissions
- tasks:read
- tasks:write
- messages:read
- messages:write
- projects:read
- projects:write
- chats:read
- files:read
- files:write
Read tasks (tasks:read)
curl https://gateway.edworking.com/ \
-H "Authorization: Bearer $EDWORKING_API_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"query":"{ apiTasks(limit: 50) { id name projectId updatedAt } }"}'Create a task (tasks:write)
mutation CreateTask($projectId: ID!, $name: String!) {
apiCreateTask(projectId: $projectId, name: $name) {
id
name
projectId
}
}Read the full API reference
Create a token in Profile settings, API tokens. Choose permissions and expiry, then reauthenticate to reveal it once. The reference lists all supported operations and migration limits.
Import and migration
Move your Existing Projects in One Pass
The import assistant is already in your workspace. Pick a source, drop in the export, and Edworking creates a copy of your projects. Nothing keeps syncing afterwards, so plan it as a cutover.
Import
Import assistant
Asana
ClickUp
Jira
Monday
Notion
Trello
| Source | Accepted export | What comes across | Not imported |
|---|---|---|---|
| Asana | CSV or XLSX | Tasks, subtasks, projects, status, due dates, tags and assignees | Custom fields, rules, forms, portfolios, dependencies and comment history |
| ClickUp | CSV | Tasks, hierarchy, status, priorities, estimates, lists, tags and selected attachments | Automations, custom fields, dashboards, goals and dependency links |
| Jira | CSV | Issues, subtasks, status, priority, estimates, epics and comments | Workflow rules, screens and schemes, sprints, custom field configuration and issue links |
| Monday | XLSX or CSV | Tasks, boards, statuses, priorities, dates and owners | Automations, integrations, formula and mirror columns, dashboards and board views |
| Notion | Export ZIP | Tasks and docs, depending on which export type you choose | Relations and rollups, synced blocks, formulas, page permissions and embedded databases |
| Trello | CSV | Cards, boards, lists, labels, members and due dates | Power-Ups, automations, checklists, card comments and attachments |
The assistant shows the export steps for the source you pick. Attachments only travel with ClickUp exports, unmatched assignees arrive unassigned, and your data in the original tool is never touched. Import into an empty space so a second run cannot merge into existing work.
Integration planning
Connect specialist tools without scattering the work
Use Edworking integrations when an outside app still matters, but keep ownership, decisions, files, and follow-up in the workspace where the team actually executes.
Which apps should be integrated?
Connect calendar, repository, form, CRM, support, finance, or automation tools when they create events that need team action, review, or documentation.
When should a team consolidate instead?
Consolidate when teammates copy the same update across chat, docs, tasks, files, and meetings just to keep context visible.
How do integrations support tool-sprawl audits?
Start by connecting the tools that must remain, then replace duplicate chat, meeting, task, and file handoff tools once the daily workflow is visible in one place.
Best integration candidates
- Google Calendar events that need prep or follow-up
- GitHub issues and pull requests that affect project delivery
- Zapier or Pabbly automations that create repeatable team tasks
- Specialist systems that remain the source of truth for one workflow
Better to consolidate
- Chat channels used as task lists
- Meeting notes that need manual follow-up elsewhere
- Files passed around without owners or deadlines
- Project updates copied into several tools for visibility
Connect your Stack, then Keep the Work Together
Start on the free plan, connect Google Calendar and GitHub, and move up to Business when you need the API or an automation platform.
No credit card required. Free guided migration from your current tool.
Explore More Resources
Discover guides, tools, and insights to help you succeed
Frequently Asked Questions
A native integration is built into Edworking and stays connected, so Google Calendar and GitHub keep reflecting changes after setup. An automation runs on Zapier or Pabbly Connect and fires once per event, so you pay that platform and it sits between the two apps. An import is a one-time file transfer from a tool such as Asana or Jira, and nothing keeps syncing once it finishes.
Google Calendar and GitHub are available on all plans. The GraphQL API, Zapier and Pabbly Connect require the Business plan. The import assistant is available on every plan, including the free one.
It works in both directions for visibility. You can see your selected Google calendars inside Edworking, and Edworking task deadlines can appear in your calendar view. Editing an event in one system and having that edit apply in the other is not documented, so do not plan around it.
You install the Edworking GitHub App on the repositories you choose. From there you can create Edworking tasks from GitHub issues, pick the default space those issues land in, keep pull-request status visible on the linked task, and link work automatically using an Edworking task ID. You can reconfigure or disconnect the installation at any time.
No. Zapier offers triggers, actions and task search. Pabbly Connect offers actions such as creating tasks, projects and messages. The catalogs and authentication methods differ. Scoped API tokens require explicit connector support; do not paste them into a password field.
Use scoped API tokens with https://gateway.edworking.com/. Read and create tasks, messages, projects and files; update task names and due dates, and list private chats and project statuses. Read and write permissions are separate. Account operations, WebSocket subscriptions and ordinary REST endpoints are excluded. Tokens expire after 7, 30 or 90 days and can be rotated or revoked.
Asana, ClickUp, Jira, Monday, Notion and Trello. The import assistant in your workspace shows the export steps for the source you pick, then walks you through uploading the file, reviewing what it found and confirming the import. Tasks, hierarchy, status, dates and assignee names move across. Automations, custom field configuration and most attachments do not.
Yes. You can run the import yourself from the assistant in your workspace, and if you would rather not, our team will run it with you at no cost and confirm the result before you retire the old tool.