Skip to content

Conversation

@eraykeskinmac
Copy link

Proposed Content
I would like to propose adding 5 community tools to the Community Tools documentation, each as separate files following the utcp.md format.

Added Tools:

1. strands-hubspot

2. strands-teams

3. strands-telegram

4. strands-telegram-listener

5. strands-deepgram

Format Compliance
Each tool file follows the established pattern from utcp.md:

  • {{ community_contribution_banner }} included
  • Package description and purpose
  • Installation instructions
  • Usage examples with code snippets
  • Key features list
  • Configuration requirements
  • Resource links (PyPI, GitHub)

Community Value
These tools fill critical gaps in the Strands ecosystem:

  • Enterprise Communication: Teams integration for workplace workflows
  • CRM Integration: Safe HubSpot data access for sales intelligence
  • Global Messaging: Telegram ecosystem (800M+ users) with full send/receive
  • Speech Processing: AI-powered transcription and audio intelligence
  • Production Ready: All tools have comprehensive error handling and type safety

Add comprehensive documentation for community-contributed tools:

- strands-hubspot: READ-ONLY HubSpot CRM integration with safe data access
- strands-teams: Microsoft Teams notifications with Adaptive Cards
- strands-telegram: Complete Telegram Bot API with 60+ methods
- strands-telegram-listener: Real-time message processing with AI auto-replies
- strands-deepgram: Speech & audio processing with 30+ language support

Each tool follows the community contribution format with:
- Installation instructions
- Usage examples
- Key features
- Configuration requirements
- Resource links

All tools are production-ready with comprehensive error handling,
type safety, and detailed documentation for community adoption.
Copy link
Member

@zastrowm zastrowm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for these, looking pretty good and almost ready to merge.

I've left a couple of comments - could we update the entries to:

  • Have some yaml frontmatter (not blocking, but helpful)
  • Update the links in the entry paragraph (per comments)
  • (nit - align Requried/Optional comments)


{{ community_contribution_banner }}

[strands-deepgram](https://pypi.org/project/strands-deepgram/) is a production-ready speech and audio processing tool for [Strands Agents SDK](https://github.com/strands-agents/sdk-python), powered by Deepgram's AI platform with 30+ language support.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we remove the links to Strands-Agent SDK? Given that we're on the docs, I don't think we need them.

Let's also have the first link be to the github project - I feel like most developers are going to be judging packages based on GitHub

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we link to Deepgram here too?

@@ -0,0 +1,53 @@
# strands-deepgram
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we have front-matter content on each of these packages?

Maybe:

project:
    pypi: https://pypi.org/project/strands-deepgram/
    github: https://github.com/eraykeskinmac/strands-deepgram 
    maintainer: eraykeskinmac
service:
    name: deepgram
    link: https://console.deepgram.com/

I know none of the other pages have this content, but I think going forward it would be beneficial

Comment on lines +43 to +45
DEEPGRAM_API_KEY=your_deepgram_api_key # Required
DEEPGRAM_DEFAULT_MODEL=nova-3 # Optional
DEEPGRAM_DEFAULT_LANGUAGE=en # Optional
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
DEEPGRAM_API_KEY=your_deepgram_api_key # Required
DEEPGRAM_DEFAULT_MODEL=nova-3 # Optional
DEEPGRAM_DEFAULT_LANGUAGE=en # Optional
DEEPGRAM_API_KEY=your_deepgram_api_key # Required
DEEPGRAM_DEFAULT_MODEL=nova-3 # Optional
DEEPGRAM_DEFAULT_LANGUAGE=en # Optional

Comment on lines +54 to +55
HUBSPOT_API_KEY=your_hubspot_api_key # Required
HUBSPOT_DEFAULT_LIMIT=100 # Optional
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
HUBSPOT_API_KEY=your_hubspot_api_key # Required
HUBSPOT_DEFAULT_LIMIT=100 # Optional
HUBSPOT_API_KEY=your_hubspot_api_key # Required
HUBSPOT_DEFAULT_LIMIT=100 # Optional

HUBSPOT_DEFAULT_LIMIT=100 # Optional
```

Get your API key at: [app.hubspot.com/private-apps](https://app.hubspot.com/private-apps)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The build is flagging this as not existing and it doesn't resolve for me - Is there a different page that we can link to?

@zastrowm
Copy link
Member

Are any of these replaced by https://github.com/eraykeskinmac/strands-tools-community? And/or did you want to call out https://github.com/eraykeskinmac/strands-tools-community in any of these pages?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants