Description
Overview
This automation workflow performs sentiment-driven content curation by analyzing social media posts and form submissions to identify positive feedback. This orchestration pipeline integrates scheduled Twitter searches with webhook intake, applying no-code integration for sentiment analysis using Google Cloud Natural Language API. The workflow triggers on a fixed interval of every 30 minutes and via HTTP POST webhooks, targeting English-language tweets containing specific keywords and user-submitted forms respectively.
Key Benefits
- Automates retrieval and sentiment assessment of recent tweets mentioning defined keywords every 30 minutes.
- Filters out retweets and tweets older than 30 minutes to maintain relevance in the automation workflow.
- Processes incoming form submissions via webhook, extracting and analyzing text content in real time.
- Applies sentiment thresholds to store only positively scored entries, improving data quality in the orchestration pipeline.
Product Overview
This automation workflow initiates on two distinct triggers: a time-based interval node firing every 30 minutes and an HTTP POST webhook receiving form submissions. The Twitter search node queries recent English tweets containing the keywords “strapi” or “n8n.io” in extended tweet mode, ensuring full text availability. Incoming tweets are simplified by removing URLs and extracting author details, timestamp, and tweet URL. A conditional node excludes retweets and tweets older than 30 minutes. The filtered tweets undergo sentiment analysis via Google Cloud Natural Language API. Positive tweets, defined by a sentiment score above 0.3, are then stored in a Strapi CMS instance under the “posts” content type.
Simultaneously, the webhook accepts form submissions with structured fields. The payload is simplified by extracting author and content data and timestamping with the current ISO date. The form content is analyzed with the same sentiment API, but with a higher positive threshold of 0.4. Positively scored form submissions are also stored in Strapi. The entire workflow uses OAuth2 credentials for API authentication and merges sentiment results back into source data for deterministic processing. Error handling relies on platform defaults without explicit retry logic.
Features and Outcomes
Core Automation
This no-code integration workflow ingests tweets and form content, applies sentiment analysis, and conditionally stores positive data. It uses decision nodes to filter retweets, old tweets, and negative sentiments, ensuring only relevant, positive content proceeds.
- Single-pass evaluation of tweets and form submissions for sentiment classification.
- Deterministic filtering based on retweet status and age for social media intake.
- Consistent data transformation with URL removal and author formatting.
Integrations and Intake
The workflow integrates directly with Twitter API via OAuth1 for searching tweets and with Google Cloud Natural Language API via OAuth2 for sentiment analysis. It also accepts HTTP POST webhook data structured as form fields. The Twitter search node requires English-language filters and keyword matching.
- Twitter API for keyword-based, recent tweet retrieval with extended tweet mode.
- Google Cloud Natural Language API for sentiment scoring of textual content.
- Webhook intake for structured form submissions with JSON payload extraction.
Outputs and Consumption
Positive sentiment entries are stored asynchronously in Strapi CMS as “posts” content type. Stored data fields include cleaned content, author information, creation timestamps, and URLs for tweets. The workflow ensures only positive entries exceeding defined sentiment thresholds are persisted.
- Structured records with Content, Author, Created, and URL fields saved in Strapi.
- Asynchronous data persistence triggered by conditional sentiment checks.
- Excludes negative or neutral sentiment data from storage, optimizing CMS content quality.
Workflow — End-to-End Execution
Step 1: Trigger
The workflow initiates on a schedule node firing every 30 minutes and on receiving HTTP POST requests at a configured webhook endpoint. The webhook expects form data structured in JSON, while the interval trigger initiates a Twitter search.
Step 2: Processing
Twitter search results are parsed to extract tweet text, author details, creation date, and URLs with URLs removed from text content via regex. Form submission payloads are simplified by extracting specific form fields. Basic presence checks are performed; no advanced schema validation is implemented.
Step 3: Analysis
Both tweet and form content are analyzed using Google Cloud Natural Language API. Sentiment scores are evaluated against thresholds: >0.3 for tweets and >0.4 for forms. Retweets and tweets older than 30 minutes are filtered out before analysis to maintain relevance.
Step 4: Delivery
Entries meeting positive sentiment criteria are asynchronously stored in Strapi CMS under the posts content type. Stored fields include content, author, creation timestamp, and URL (if applicable). The workflow does not persist data otherwise and relies on platform default error handling.
Use Cases
Scenario 1
An organization needs to monitor recent positive social media mentions of its product. This workflow automates scheduled searches for relevant tweets, filters out irrelevant or negative posts, and stores only positive feedback. The result is a curated dataset of favorable social impressions updated every 30 minutes.
Scenario 2
A company collects customer feedback via web forms and requires automated sentiment analysis. Incoming submissions are analyzed in real time through the webhook intake, with only positively scored entries stored for further review. This ensures actionable positive feedback is reliably captured without manual intervention.
Scenario 3
Developers or analysts need a combined pipeline that integrates social media monitoring with direct user input analysis. This orchestration pipeline supports both data sources simultaneously, performing sentiment analysis and conditional storage in a unified content management system for comprehensive insight collection.
How to use
To implement this automation workflow, import it into an n8n environment with configured OAuth credentials for Twitter and Google Cloud Natural Language API, as well as Strapi CMS access. Configure the webhook node endpoint to receive form submissions. Ensure the interval node is enabled to trigger Twitter searches every 30 minutes. Once running, the workflow will autonomously process incoming data streams, analyze sentiment, and store positively scored content in Strapi. Users can expect structured content records reflecting filtered and sentiment-validated inputs from both sources.
Comparison — Manual Process vs. Automation Workflow
| Attribute | Manual/Alternative | This Workflow |
|---|---|---|
| Steps required | Multiple manual searches, filtering, sentiment evaluation, and data entry. | Single automated pipeline combining search, filtering, analysis, and storage. |
| Consistency | Variable, dependent on human judgment and timing. | Deterministic filtering and scoring with fixed sentiment thresholds. |
| Scalability | Limited by manual processing capacity and frequency. | Scales automatically with scheduled triggers and webhook events. |
| Maintenance | High, requiring continuous manual effort and oversight. | Low, relying on stable API credentials and minimal configuration changes. |
Technical Specifications
| Environment | n8n workflow automation platform |
|---|---|
| Tools / APIs | Twitter API (OAuth1), Google Cloud Natural Language API (OAuth2), Strapi CMS API |
| Execution Model | Event-driven with scheduled interval and webhook triggers |
| Input Formats | JSON payloads from Twitter API and HTTP POST webhook form submissions |
| Output Formats | Structured JSON records stored in Strapi CMS (Content, Author, Created, URL) |
| Data Handling | Transient processing with no persistent storage except for positive sentiment entries |
| Known Constraints | Relies on external API availability and OAuth credential validity |
| Credentials | OAuth1 for Twitter, OAuth2 for Google Cloud Natural Language, API key for Strapi CMS |
Implementation Requirements
- Valid OAuth1 credentials configured for Twitter API access with appropriate permissions.
- OAuth2 credentials for Google Cloud Natural Language API enabling sentiment analysis.
- Strapi CMS instance with API access configured for storing posts content type.
Configuration & Validation
- Verify OAuth credentials for Twitter and Google Cloud APIs are correctly linked and authorized in n8n.
- Confirm the webhook node’s HTTP POST endpoint is reachable and receiving valid form submissions.
- Test the scheduled Twitter search trigger and validate that positive sentiment entries are stored in Strapi.
Data Provenance
- Trigger nodes: “Every 30 Minutes” interval and “Webhook” HTTP POST listener.
- Processing nodes: “Simplify Result” and “Simplify Webhook Result” for data extraction and cleansing.
- Sentiment analysis nodes: “Analyze Tweet” and “Analyze Form Submission” using Google Cloud Natural Language API.
FAQ
How is the sentiment-driven automation workflow triggered?
The workflow activates on a scheduled interval every 30 minutes for Twitter searches and on receiving HTTP POST webhook requests for form submissions.
Which tools or models does the orchestration pipeline use?
The pipeline uses the Twitter API for data intake and Google Cloud Natural Language API for sentiment analysis within the workflow.
What does the response look like for client consumption?
Positive sentiment content is stored asynchronously in Strapi CMS with fields including cleaned Content, Author information, creation timestamp, and URL when applicable.
Is any data persisted by the workflow?
Only positively scored tweets and form submissions are persisted to Strapi CMS; all other data is transient and discarded.
How are errors handled in this integration flow?
Error handling relies on n8n platform defaults with no explicit retry or backoff mechanisms configured in the workflow.
Conclusion
This sentiment-driven automation workflow consolidates social media monitoring and form submission analysis into a deterministic pipeline that stores only positively scored content in a centralized CMS. It leverages scheduled triggers and webhook events combined with Google Cloud Natural Language API to deliver consistent, quality-filtered data. The workflow requires valid OAuth credentials and depends on external API availability, which is a key operational consideration. Its design emphasizes reliability, relevance, and structured data curation without manual intervention or persistent intermediate storage.
Reviews
There are no reviews yet.