Skip to content

Commit 5f0eaad

Browse files
authored
Merge pull request #36 from rtCamp/develop
Update README
2 parents 59d7224 + 61b7ce9 commit 5f0eaad

File tree

1 file changed

+42
-16
lines changed

1 file changed

+42
-16
lines changed

README.md

Lines changed: 42 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,47 @@
1-
## Frappe Gmail Thread
1+
# Frappe Gmail Thread
22

3-
This app introduces Gmail thread tracking within Frappe by leveraging Gmail's Thread ID, enabling a more organized and seamless communication experience. Similar to Gmail's native threaded view, this feature groups related emails into cohesive conversations. Thread IDs are stored within Gmail Thread doctype designed specifically for threaded conversations.
3+
A Frappe app that integrates with Gmail's Thread ID to seamlessly sync and track email conversations within your Frappe/ERPNext instance. This provides a unified view of your communications, allowing you to link email threads directly to ERPNext documents like Leads, Sales Orders, and Tasks.
44

5-
Additionally, Gmail thread can be associated with any doctype, such as Lead, Sales Orders or Tasks, to efficiently track email activity within specific documents.
5+
### [View the GitHub Wiki for Full Documentation](https://github.com/rtCamp/frappe-gmail-thread/wiki "null")
66

7-
#### Key Features and Capabilities
8-
##### Send/Receive Emails:
9-
Emails sent or received will automatically sync into ERPNext.
10-
##### Link Threads to ERPNext Documents:
11-
Associate Gmail threads with any doctype (e.g., Sales Order, Task) to track email activity directly within the document.
12-
##### CC/BCC Functionality:
13-
Emails with CC/BCC recipients allow all involved users to view and interact with the thread.
14-
##### Attachments:
15-
Email attachments are linked to the Gmail thread and are visible in the associated document's activity if the thread is linked.
16-
##### Involving Additional Users:
17-
Add users manually to the Involved User field within the Gmail Thread. These users can interact with the thread even if they weren’t originally part of the email thread.
7+
## Key Features
188

19-
#### License
9+
- **Seamless Email Syncing:** Automatically syncs sent and received emails into your Frappe instance.
2010

21-
agpl-3.0
11+
- **Threaded Conversations:** Organizes emails into cohesive threads based on Gmail's native Thread ID.
12+
13+
- **Document Linking:** Link email threads to any ERPNext doctype to view communication history in the document's activity feed.
14+
15+
- **Multi-User Visibility:** Emails with CC/BCC recipients automatically grant all involved users access to the thread.
16+
17+
- **Attachment Management:** Attachments are linked to the thread and visible within the associated document.
18+
19+
- **Manual User Access:** Manually add users to a thread to grant them access to the conversation.
20+
21+
- **Selective Syncing:** Use Gmail labels to control which emails are synced to Frappe, giving you granular control over what data is stored.
22+
23+
## Installation
24+
25+
Run the following command to install the app.
26+
27+
```bash
28+
bench get-app git@github.com:rtCamp/frappe-gmail-thread.git
29+
bench --site [site-name] install-app frappe_gmail_thread
30+
bench --site [site-name] migrate
31+
bench restart
32+
```
33+
34+
For local development, check out our dev-tool for seamlessly building Frappe apps: [frappe-manager](https://github.com/rtCamp/Frappe-Manager)
35+
NOTE: If using `frappe-manager`, you might require to `fm restart` to provision the worker queues.
36+
37+
## License
38+
39+
This project is licensed under the [AGPLv3 License](license.txt).
40+
41+
## Technical Details
42+
43+
The app uses email message IDs and reference headers to group emails into a single `Gmail Thread` doctype, unifying threads across different user mailboxes within Frappe.
44+
45+
## Contributing
46+
47+
We welcome contributions! If you encounter any bugs or have suggestions, please open an issue or submit a pull request on our GitHub repository. Make sure to read [contribution.md](./CONTRIBUTING.md) for details.

0 commit comments

Comments
 (0)