← All guides

Integrations and AI · Taskending editorial team

Connect Gmail to receive project requests

Google sign-in and Gmail intake need different permissions. A project connection brings new messages from a selected mailbox into the workflow.

· 1 min read

How to apply it

An authorized administrator starts Gmail setup in Taskending project settings. Select the right Google account and review read-only access. New inbox messages arriving after connection are checked approximately once a minute and processed into project issues or comments.

A concrete example

A “My report is empty” message to the support mailbox can become a request. Later messages in the conversation can be associated with existing context. Check project and customer information on the first example.

What to watch for

This is not an automatic migration of the entire historical mailbox. The connection does not send, modify or delete Gmail messages. Choose an appropriate project mailbox rather than an unrelated personal inbox.

How to check the outcome

Verify that a permitted new message reaches the correct record. Keep inbound intake separate from outbound email delivery.

Try it in your own workflow.

Create a company workspace and your first issue. Taskending is currently free.

Start for free

Keep reading

01
Integrations and AI

AI task management with Codex and MCP

Connect Codex to issue context through MCP. A human-reviewed workflow for assigned tasks, progress notes, status updates and time tracking.

02
Integrations and AI

How to connect a GitHub repository to Taskending

Signing in with GitHub and connecting a project repository are separate actions. Repository access is authorized separately to associate code events with work.

03
Integrations and AI

Use issue keys in Git branch names

An issue key connects a code change with its reason. Consistent use in branch names makes context easier to find.