-
Notifications
You must be signed in to change notification settings - Fork 9
Attio connection #171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Attio connection #171
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds comprehensive documentation and configuration for Attio CRM integration with Hypermode. The purpose is to enable users to connect their Hypermode agents to Attio for automated CRM operations including managing companies, deals, and customer relationships.
- Adds complete documentation for setting up and using Attio CRM connection
- Updates navigation structure to organize connections by category (CRMs vs Data Sources)
- Adds "CRMAgent" to the accepted vocabulary for style checking
Reviewed Changes
Copilot reviewed 3 out of 13 changed files in this pull request and generated 2 comments.
File | Description |
---|---|
agents/connections/attio.mdx | Complete documentation guide for Attio CRM integration with setup instructions, examples, and troubleshooting |
docs.json | Updates navigation structure to categorize connections and adds Attio documentation page |
styles/config/vocabularies/general/accept.txt | Adds "CRMAgent" to accepted vocabulary list |
update companies and deals, search for existing records, manage deal | ||
pipelines, and track customer interactions. Always confirm data before making | ||
changes and provide clear summaries of actions taken. | ||
- **Model**: GPT-4.1 - Default - Optionally, use Claude for best results |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nitpick] The model recommendation format is inconsistent and unclear. Consider using a more structured format like 'GPT-4.1 (Default) or Claude (Recommended for best results)'.
- **Model**: GPT-4.1 - Default - Optionally, use Claude for best results | |
- **Model**: GPT-4.1 (Default) or Claude (Recommended for best results) |
Copilot uses AI. Check for mistakes.
Move the deal through your pipeline: | ||
|
||
```text | ||
Add a note about the "Enterprise Software License - TechCorp" deal that the demo completed yesterday. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The deal name in the example ('Enterprise Software License - TechCorp') doesn't match the deal created in Test 3 ('Q1 Enterprise Software License' with 'Tech Solutions Inc'). This inconsistency could confuse users following the tutorial.
Add a note about the "Enterprise Software License - TechCorp" deal that the demo completed yesterday. | |
Add a note about the "Q1 Enterprise Software License" deal with "Tech Solutions Inc" that the demo completed yesterday. |
Copilot uses AI. Check for mistakes.
"agents/connections/supabase", | ||
"agents/connections/neo4j" | ||
{ | ||
"group": "CRMs", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's make sure these sub-groups match the categories used on the "Available Connections" page. So the sub-group names here would be "Sales" and "Database"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we also include the "Details" button and number of tools pill in the "Available Connections" page?
No description provided.