feat(gmail): migrate Gmail integration from private repo#323
Merged
Conversation
Migrates the Gmail integration from the private `integrations` repo to the public `autohive-integrations` repo after a security/safety/secrets review found no hardcoded secrets, internal URLs, customer references, or proprietary business logic. Drops legacy artefacts that don't belong in the public repo: * integration.py — vendored old SDK copy (public uses PyPI package) * test_gmail_integration.py — manual harness (replaced by tests/) Includes 21 actions across messages, threads, drafts, and labels, with HTML sanitisation via bleach and pagination on every list endpoint. Closes #322
🔍 Integration Validation ResultsCommit: Changed directories:
|
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
| import sys | ||
|
|
||
| sys.path.insert(0, os.path.abspath(os.path.join(os.path.dirname(__file__), ".."))) | ||
| from gmail import gmail # noqa: F401 |
| @@ -0,0 +1,6 @@ | |||
| import context # noqa: F401 | |||
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4e0f3b8faa
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
Comment on lines
+476
to
+483
| # Handle CC recipients if present | ||
| if "cc" in inputs: | ||
| if isinstance(inputs["cc"], list): | ||
| message["cc"] = ", ".join(inputs["cc"]) | ||
| else: | ||
| message["cc"] = inputs["cc"] | ||
|
|
||
| message["subject"] = inputs["subject"] |
There was a problem hiding this comment.
When users send a new email, the implementation copies only to and cc into the MIME message and then immediately sets the subject, so any BCC support advertised in gmail/README.md/the root README is unavailable for send_email (and direct callers passing bcc would silently drop those recipients). Draft creation/update already handles bcc, so mirror that logic here and expose the field in this action's schema.
Useful? React with 👍 / 👎.
Comment on lines
+848
to
+851
| return parsedate_to_datetime(email["date"]) | ||
| except Exception: | ||
| # Fallback: use the email ID as a rough ordering mechanism | ||
| return email["id"] |
There was a problem hiding this comment.
If a thread contains one message with a parseable Date header and another with a missing or malformed Date, this fallback returns a string while the successful path returns a datetime; Python 3 cannot compare those key types, so thread_emails.sort(...) raises and the whole get_thread_emails action returns an error for that thread. Use a single comparable key type for both paths, such as a tuple with a parse-success flag and timestamp/id.
Useful? React with 👍 / 👎.
Collaborator
Author
|
Please ignore all the warnings in this PR - this is a 1:1 migration and will be fixed up in a subsequent PR. |
ProRedCat
approved these changes
May 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #322
Summary
Migrates the Gmail integration from the private
Autohive-AI/integrationsrepo to the publicautohive-integrationsrepo.Security / safety / secrets review
Reviewed before migration — clean:
integration.py)autohive-integrations-sdkfrom PyPItest_gmail_integration.py)What's included
gmail/config.json— copied as-isgmail/gmail.py— copied as-is (usesgoogleapiclient+bleachfor HTML sanitisation)gmail/icon.png— copied as-isgmail/__init__.py— empty (matches public repo convention)gmail/requirements.txt— kept at SDK~=1.0.2(migrate as-is; SDK 2.0 upgrade is a separate concern)gmail/README.md— rewritten in the public repo style (modelled ongoogle-calendar/README.md)gmail/tests/{__init__.py,context.py,test_gmail.py}— copied placeholder structureREADME.md— added Gmail entry near other Google integrationsValidation
Companion PRs
gmail/)migrating-private-integrationskill)