Scheduled Auto-Replies to Targeted Tweets using X (Twitter) API

This n8n workflow automates the process of fetching tweets and then conditionally performing an action based on their content. It's designed to run on a schedule, making it suitable for periodic monitoring and response.

What it does

This workflow performs the following steps:

1. Triggers on a Schedule: The workflow starts at predefined intervals (e.g., every hour, daily).
2. Makes an HTTP Request: It initiates an HTTP request, likely to an API (such as the X/Twitter API, given the directory name) to fetch data. The specific endpoint and parameters would need to be configured within the "HTTP Request" node.
3. Filters Data with Conditional Logic: It then uses an "If" node to evaluate the data received from the HTTP request. This node allows for conditional branching, meaning subsequent actions will only occur if the data meets specific criteria.
4. Transforms Data (Conditional): If the condition in the "If" node is met, the workflow proceeds to an "Edit Fields (Set)" node. This node is used to manipulate or add fields to the data, preparing it for the next step.
5. Executes Custom Code (Conditional): Following the data transformation, a "Code" node is executed. This node allows for custom JavaScript logic, which could be used for advanced data processing, formatting, or even interacting with other services not directly supported by n8n nodes.
6. Provides Notes: A "Sticky Note" is included, likely for documentation or temporary notes within the workflow design.

Prerequisites/Requirements

• n8n Instance: A running n8n instance to import and execute the workflow.
• API Endpoint: Access to an API that can be queried via HTTP. Based on the directory name, this is likely the X (Twitter) API.
• API Credentials: Any necessary API keys, tokens, or authentication details for the target API (e.g., X/Twitter API credentials) configured as n8n credentials.
• Understanding of JavaScript: For customizing the "Code" node.

Setup/Usage

1. Import the Workflow: Import the provided JSON into your n8n instance.
2. Configure Credentials:
   • Set up the necessary credentials for the "HTTP Request" node if it requires authentication (e.g., API Key, OAuth2 for X/Twitter).
3. Configure the HTTP Request Node (ID: 19):
   • Specify the URL for the API endpoint you wish to query.
   • Set the HTTP method (e.g., GET, POST).
   • Add any required headers, query parameters, or body content to fetch the desired data (e.g., search queries for tweets).
4. Configure the Schedule Trigger Node (ID: 839):
   • Adjust the "Schedule Trigger" node to your desired frequency for running the workflow (e.g., every 15 minutes, once a day).
5. Configure the If Node (ID: 20):
   • Define the conditions under which the workflow should proceed. For example, you might check for specific keywords in the tweet text, certain user IDs, or other criteria from the API response.
6. Configure the Edit Fields (Set) Node (ID: 38):
   • If the "If" condition is met, configure this node to transform the data as needed before it reaches the custom code. This could involve extracting specific fields, renaming them, or creating new ones.
7. Configure the Code Node (ID: 834):
   • Write your custom JavaScript code to perform the desired action. If the goal is to auto-reply to tweets, this node would likely contain logic to construct the reply and then make another API call (e.g., to the X/Twitter API's tweet reply endpoint) using an httpRequest function within the code, or by passing the processed data to another HTTP Request node downstream.
8. Activate the Workflow: Once configured, activate the workflow to start it running on its schedule.