Aws news monitoring & LinkedIn content automation with Claude 3 & Feishu
AWS News Analysis and LinkedIn Automation Pipeline
Transform AWS industry news into engaging LinkedIn content with AI-powered analysis and automated approval workflows.
Who's it for
This template is perfect for:
- Cloud architects and DevOps engineers who want to stay current with AWS developments
- Content creators looking to automate their AWS news coverage
- Marketing teams needing consistent, professional AWS content
- Technical leaders who want to share industry insights on LinkedIn
- AWS consultants building thought leadership through automated content
How it works
This workflow creates a comprehensive AWS news analysis and content generation pipeline with two main flows:
Flow 1: News Collection and Analysis
- Scheduled RSS Monitoring: Automatically fetches latest AWS news from the official AWS RSS feed daily at 8 PM
- AI-Powered Analysis: Uses AWS Bedrock (Claude 3 Sonnet) to analyze each news item, extracting:
- Professional summary
- Key themes and keywords
- Importance rating (Low/Medium/High)
- Business impact assessment
- Structured Data Storage: Saves analyzed news to Feishu Bitable with approval status tracking
Flow 2: LinkedIn Content Generation
- Manual Approval Trigger: Feishu automation sends approved news items to the webhook
- AI Content Creation: AWS Bedrock generates professional LinkedIn posts with:
- Attention-grabbing headlines
- Technical insights from a Solutions Architect perspective
- Business impact analysis
- Call-to-action engagement
- Automated Publishing: Posts directly to LinkedIn with relevant hashtags
How to set up
Prerequisites
- AWS Bedrock access with Claude 3 Sonnet model enabled
- Feishu account with Bitable access
- LinkedIn company account with posting permissions
- n8n instance (self-hosted or cloud)
Detailed Configuration Steps
1. AWS Bedrock Setup
Step 1: Enable Claude 3 Sonnet Model
- Log into your AWS Console
- Navigate to AWS Bedrock
- Go to Model access in the left sidebar
- Find Anthropic Claude 3 Sonnet and click Request model access
- Fill out the access request form (usually approved within minutes)
- Once approved, verify the model appears in your Model access list
Step 2: Create IAM User and Credentials
- Go to IAM Console
- Click Users → Create user
- Name:
n8n-bedrock-user - Attach policy:
AmazonBedrockFullAccess(or create custom policy with minimal permissions) - Go to Security credentials tab → Create access key
- Choose Application running outside AWS
- Download the credentials CSV file
Step 3: Configure in n8n
- In n8n, go to Credentials → Add credential
- Select AWS credential type
- Enter your Access Key ID and Secret Access Key
- Set Region to your preferred AWS region (e.g.,
us-east-1) - Test the connection
Useful Links:
2. Feishu Bitable Configuration
Step 1: Create Feishu Account and App
- Sign up at Feishu International
- Create a new Bitable (multi-dimensional table)
- Go to Developer Console → Create App
- Enable Bitable permissions in your app
- Generate App Token and App Secret
Step 2: Create Bitable Structure
-
Create a new Bitable with these columns:
title(Text)pubDate(Date)summary(Long Text)keywords(Multi-select)rating(Single Select: Low, Medium, High)link(URL)approval_status(Single Select: Pending, Approved, Rejected)
-
Get your App Token and Table ID:
- App Token: Found in app settings
- Table ID: Found in the Bitable URL (
tbl...)
Step 3: Set Up Automation
- In your Bitable, go to Automation → Create automation
- Trigger: When field value changes → Select
approval_statusfield - Condition: approval_status equals "Approved"
- Action: Send HTTP request
- Method: POST
- URL: Your n8n webhook URL (from Flow 2)
- Headers:
Content-Type: application/json - Body:
{{record}}
Step 4: Configure Feishu Credentials in n8n
- Install Feishu Lite community node (self-hosted only)
- Add Feishu credential with your App Token and App Secret
- Test the connection
Useful Links:
3. LinkedIn Company Account Setup
Step 1: Create LinkedIn App
- Go to LinkedIn Developer Portal
- Click Create App
- Fill in app details:
- App name:
AWS News Automation - LinkedIn Page: Select your company page
- App logo: Upload your logo
- Legal agreement: Accept terms
- App name:
Step 2: Configure OAuth2 Settings
- In your app, go to Auth tab
- Add redirect URL:
https://your-n8n-instance.com/rest/oauth2-credential/callback - Request these scopes:
w_member_social(Post on behalf of members)r_liteprofile(Read basic profile)r_emailaddress(Read email address)
Step 3: Get Company Page Access
- Go to your [LinkedIn Company Page](ex. https://www.linkedin.com/company/105783641)
- Navigate to Admin tools → Manage admins
- Ensure you have Content admin or Super admin role
- Note your Company Page ID (found in page URL)
Step 4: Configure LinkedIn Credentials in n8n
- Add LinkedIn OAuth2 credential
- Enter your Client ID and Client Secret
- Complete OAuth2 flow by clicking Connect my account
- Select your company page for posting
Useful Links:
4. Workflow Activation
Final Setup Steps:
- Import the workflow JSON into n8n
- Configure all credential connections:
- AWS Bedrock credentials
- Feishu credentials
- LinkedIn OAuth2 credentials
- Update webhook URL in Feishu automation to match your n8n instance
- Activate the scheduled trigger (daily at 8 PM)
- Test with manual webhook trigger using sample data
- Verify Feishu Bitable receives data
- Test approval workflow and LinkedIn posting
Requirements
Service Requirements
- AWS Bedrock with Claude 3 Sonnet model access
- AWS account with Bedrock service enabled
- IAM user with Bedrock permissions
- Model access approval for Claude 3 Sonnet
- Feishu Bitable for news storage and approval workflow
- Feishu account (International or Lark)
- Developer app with Bitable permissions
- Automation capabilities for webhook triggers
- LinkedIn Company Account for automated posting
- LinkedIn company page with admin access
- LinkedIn Developer app with posting permissions
- OAuth2 authentication setup
- n8n community nodes: Feishu Lite node (self-hosted only)
Technical Requirements
- n8n instance (self-hosted recommended for community nodes)
- Webhook endpoint accessible from Feishu automation
- Internet connectivity for API calls and RSS feeds
- Storage space for workflow execution logs
Cost Considerations
- AWS Bedrock: ~$0.01-0.05 per news analysis
- Feishu: Free tier available, paid plans for advanced features
- LinkedIn: Free API access with rate limits
- n8n: Self-hosted (free) or cloud subscription
How to customize the workflow
Content Customization
- Modify AI prompts in the AI Agent nodes to change tone, focus, or target audience
- Adjust hashtags in the LinkedIn posting node for different industries
- Change scheduling frequency by modifying the Schedule Trigger settings
Integration Options
- Replace LinkedIn with Twitter/X, Facebook, or other social platforms
- Add Slack notifications for approved content before posting
- Integrate with CRM systems to track content performance
- Add content calendar integration for better planning
Advanced Features
- Multi-language support by modifying AI prompts for different regions
- Content categorization by adding tags for different AWS services
- Performance tracking by integrating analytics platforms
- Team collaboration by adding approval workflows with multiple reviewers
Technical Modifications
- Change RSS sources to monitor other AWS blogs or competitor news
- Adjust AI models to use different Bedrock models or external APIs
- Add data validation nodes for better error handling
- Implement retry logic for failed API calls
Important Notes
Service Limitations
- This template uses community nodes (Feishu Lite) and requires self-hosted n8n
- Geo-restrictions may apply to AWS Bedrock models in certain regions
- Rate limits may affect high-frequency posting - adjust scheduling accordingly
- Content moderation is recommended before automated posting
- Cost considerations: Each AI analysis costs approximately $0.01-0.05 USD per news item
Troubleshooting Common Issues
AWS Bedrock Issues:
- Model not found: Ensure Claude 3 Sonnet access is approved in your region
- Access denied: Verify IAM permissions include Bedrock service access
- Rate limiting: Implement retry logic or reduce analysis frequency
Feishu Integration Issues:
- Authentication failed: Check App Token and App Secret are correct
- Table not found: Verify Table ID matches your Bitable URL
- Automation not triggering: Ensure webhook URL is accessible and returns 200 status
LinkedIn Posting Issues:
- OAuth2 errors: Re-authenticate LinkedIn credentials
- Posting failed: Verify company page admin permissions
- Rate limits: LinkedIn has daily posting limits for company pages
Security Best Practices
- Never hardcode credentials in workflow nodes
- Use environment variables for sensitive configuration
- Regularly rotate API keys and access tokens
- Monitor API usage to prevent unexpected charges
- Implement error handling for failed API calls
AWS News Monitoring and LinkedIn Content Automation with Claude 3
This n8n workflow automates the process of monitoring RSS feeds for news, summarizing the content using an AI agent (Claude 3 via AWS Bedrock), and then publishing these summaries as posts on LinkedIn. This helps businesses stay updated with relevant news and maintain an active social media presence with minimal manual effort.
What it does
- Triggers on Schedule: The workflow runs at a scheduled interval, checking for new content.
- Reads RSS Feed: It fetches the latest articles from a specified RSS feed.
- Generates AI Summary: For each new article, it uses an AI agent (powered by AWS Bedrock's Claude 3 model) to generate a concise summary.
- Publishes to LinkedIn: The AI-generated summary is then automatically posted as an update on LinkedIn.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- AWS Account: Configured with access to AWS Bedrock and the Claude 3 model. You will need AWS credentials (Access Key ID and Secret Access Key).
- LinkedIn Account: A LinkedIn account with the necessary permissions to post updates. You will need LinkedIn OAuth2 credentials configured in n8n.
- RSS Feed URL: The URL of the RSS feed you wish to monitor.
Setup/Usage
- Import the workflow:
- Download the provided JSON file.
- In your n8n instance, click "Workflows" in the left sidebar, then "New Workflow".
- Click the three-dot menu in the top right, select "Import from JSON", and paste the workflow JSON or upload the file.
- Configure Credentials:
- AWS Bedrock Chat Model:
- Click on the "AWS Bedrock Chat Model" node.
- Select or create a new "AWS" credential.
- Enter your AWS Access Key ID and Secret Access Key.
- Ensure the region is correctly set for your Bedrock service.
- LinkedIn:
- Click on the "LinkedIn" node.
- Select or create a new "LinkedIn OAuth2" credential.
- Follow the n8n instructions to authenticate with your LinkedIn account and grant the necessary permissions.
- AWS Bedrock Chat Model:
- Configure RSS Feed:
- Click on the "RSS Read" node.
- Update the "URL" field with the RSS feed you want to monitor.
- Configure AI Agent (Optional, for advanced tuning):
- Click on the "AI Agent" node.
- Review the "System Message" and "User Message" to ensure the AI generates summaries in your desired format and tone. You might want to instruct it to generate a summary suitable for a LinkedIn post.
- Configure Schedule Trigger:
- Click on the "Schedule Trigger" node.
- Adjust the "Interval" to your preferred frequency for checking the RSS feed (e.g., every hour, daily).
- Activate the Workflow:
- Once all credentials and configurations are set, click the "Active" toggle in the top right of the workflow editor to enable the workflow.
The workflow will now run automatically based on your schedule, fetching news, summarizing it with AI, and posting to LinkedIn.
Related Templates
Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API
Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen
Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack
📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.
Automate Gmail responses with GPT and human-in-the-loop verification
Try It Out! This n8n template uses AI to automatically respond to your Gmail inbox by drafting response for your approval via email. How it works Gmail Trigger monitors your inbox for new emails AI Analysis determines if a response is needed based on your criteria Draft Generation creates contextually appropriate replies using your business information Human Approval sends you the draft for review before sending Auto-Send replies automatically once approved Setup Connect your Gmail account to the Gmail Trigger node Update the "Your Information" node with: Entity name and description Approval email address Resource guide (FAQs, policies, key info) Response guidelines (tone, style, formatting preferences) Configure your LLM provider (OpenAI, Claude, Gemini, etc.) with API credentials Test with a sample email Requirements n8n instance (self-hosted or cloud) Gmail account with API access LLM provider API key Need Help? Email Nick @ nick@tropicflare.com