search
Ctrlk

MyBackstage

hashtag
Node: Site to Features

This node takes the URL extracted by the Caller 2 node and uses it to extract key features from the website.

  • Label: Site to Features

  • Agent: SiteScraperAgent In this example, we have selected a dummy agent called SiteScraperAgent. This agent is responsible for analyzing the given website URL and extracting key features such as product descriptions, business value propositions, and other relevant information.

  • URL: {{7.command.readSite}} The URL passed from the Caller 2 node (e.g., "https://integrail.aiarrow-up-right") is connected here for further processing. The SiteScraperAgent extracts the essential features of the website, which will be used in subsequent nodes to build a marketing strategy.

In our case, the SiteScraperAgent does exactly what is expected—scraping the website's data and passing the extracted information to be stored in the session for later use in the agent's workflow.

hashtag
Complete Agent Flow Overview with Field Values

This section will walk through each node in the agent, explaining the flow of information and the specific values of key fields like prompts, connections, and session names. This example illustrates how a website analysis agent is designed on the Integrail platform, which extracts website data and generates a marketing strategy.

hashtag
Fetch Telegram Channel Unread

The Fetch Telegram Channel Unread node is designed to retrieve unread messages from a specified Telegram channel. This is useful for automating message retrieval or monitoring updates within a channel. Below is a breakdown of the key components:

  • Label: The name of the node, by default labeled Fetch Telegram Channel Unread. You can rename it to suit the specific task or function of your workflow.

  • Link to the channel: This required field allows you to provide the link to the specific Telegram channel from which you want to fetch unread messages. The link must be accurate to retrieve the messages from the correct channel.

  • Limit: This field sets the maximum number of unread messages to fetch. For example, if set to 10, the node will retrieve up to 10 unread messages. The minimum value is 1.

  • Auth Token: This required field is for authenticating the connection to Telegram. You need to provide the appropriate authentication token, allowing the node to access the specified Telegram channel.

  • Fallback Outputs: This field allows you to define an alternative action in case there’s an issue retrieving the messages, ensuring the workflow continues smoothly.

  • Results: The fetched unread messages from the Telegram channel will be displayed here as a list, which can then be passed to subsequent nodes or used as needed.

hashtag
Usage

This node is useful for workflows that involve tracking or retrieving updates from Telegram channels. It can be integrated into a system to automate the collection of messages and updates, reducing the need for manual checks.

hashtag
Troubleshooting Tips for 401 Unauthorized Errors

If you encounter a 401 Unauthorized error after configuring the authorization:

  1. Verify Token or Credentials: Ensure the token, API key, or credentials are correct and active.

  2. Check Header Formatting: Ensure headers like Authorization and x-api-key are correctly formatted with no extra spaces.

  3. Compare with Postman: Replicate the request in Postman to confirm successful setup, then replicate settings in the Generic API Node.

  4. Review API Documentation: Double-check the API’s authentication requirements to ensure you’re following all necessary steps.

hashtag
Create a Wix blog post

The Create a Wix Blog Post node allows you to automate the creation and management of blog posts directly on a Wix site. Below is an overview of the key settings for this node:

  • Label: The name of the node, by default labeled Create a Wix blog post. You can rename it based on your specific use case.

  • Title: The title of the blog post. This field is required and will be displayed as the post’s headline on your Wix blog.

  • Featured?: This toggle allows you to mark the blog post as a featured post, which may display the post prominently on your Wix site depending on your configuration.

  • Enable Commenting?: This option allows or disallows user comments on the blog post. Toggle it on if you want readers to be able to comment.

  • Category Ids: You can categorize the blog post by providing category IDs that match categories on your Wix blog. This helps organize your content by topics.

  • Hashtags: Add relevant hashtags to the post, which can help with content discoverability and SEO. Hashtags should be added as a list.

  • Related Post Ids: You can link other related posts by providing their IDs, making it easier for readers to navigate related content.

  • Image: You can add a visual element to the blog post by uploading an image. Supported formats include .jpg, .jpeg, and .png, with a maximum file size of 500 MB.

  • Immediately Publish?: This toggle allows you to instantly publish the blog post once it is created. If disabled, the post will remain in draft mode.

  • Post Text Content: This field contains the main text of the blog post. Add all the content that you want to appear in the body of the post.

  • Auth Token: This field is required to authenticate the node's connection to your Wix account. You need to provide the authentication token to ensure that the node has permission to create and manage blog posts on your Wix site.

  • Fallback Outputs: This field allows you to specify an alternative action or output in case there’s an issue with creating the blog post, ensuring that the workflow continues smoothly.

hashtag
Usage

This node is ideal for automating the creation and management of blog posts on Wix. It streamlines the process of posting new content, adding images, setting categories, and even publishing the post instantly if needed.

hashtag
Get ClickUp Tasks

The Get ClickUp Tasks node is designed to retrieve tasks from a ClickUp workspace. This node allows you to filter and limit the tasks that are fetched based on specific parameters. Here's a breakdown of its key settings:

  • Label: The name of the node, by default labeled Get ClickUp Tasks. You can rename it based on your workflow or use case.

  • Filter By: This field allows you to set a filter for the tasks you want to retrieve. For example, you can filter by task status, priority, or other criteria set in ClickUp. The default filter is "default," but you can modify this according to your needs.

  • Limit: Specifies the number of tasks to retrieve. The minimum value is 1, and you can set it higher depending on how many tasks you want to fetch. In this example, the limit is set to 10.

  • Team ID: This required field specifies the ClickUp team from which to retrieve tasks. You need to input the Team ID corresponding to the workspace you are working within ClickUp.

  • Auth Token: This required field is for authenticating the connection to ClickUp. You must provide the appropriate authentication token to allow the node to access your ClickUp tasks.

  • Fallback Outputs: This field allows you to specify alternative actions or outputs if there’s an issue fetching the tasks, ensuring the workflow continues.

  • Results: The retrieved tasks will be displayed here in a list format as objects, which can then be used in subsequent nodes for further processing or workflow tasks.

hashtag
Usage

This node is ideal for automating the retrieval and management of ClickUp tasks in your workflow, allowing you to filter, retrieve, and process tasks based on specific conditions. It helps streamline task tracking and management for productivity.

hashtag
Get ClickUp Teams

The Get ClickUp Teams node is used to retrieve teams from a ClickUp workspace. This node allows you to fetch details of multiple teams associated with your ClickUp account. Below is a breakdown of the key settings:

  • Label: The name of the node, by default labeled Get ClickUp Teams. You can rename it according to your specific workflow.

  • Limit: This required field specifies how many teams you want to retrieve. You can set the limit to control the number of teams fetched. The minimum is 1, and in this example, it is set to 10.

  • Auth Token: This required field is for authenticating the connection to ClickUp. You need to provide the appropriate authentication token (OAuth or API key) to retrieve teams from your ClickUp workspace.

  • Fallback Outputs: This field allows you to define an alternative action or output in case the node fails to retrieve the teams, ensuring the workflow continues.

  • Results: The teams fetched from ClickUp will be displayed here in a list format as objects, which can then be used in subsequent nodes or actions.

hashtag
Usage

This node is useful for fetching teams from a ClickUp workspace, allowing you to automate workflows that involve team-based management or organization.

hashtag
Caller

The Caller node is designed to call a command and generate a response based on user inputs. Here’s how the key parameters function:

Model: Choose language model to be used for generating responses.

User Prompt: This field captures the user's input or query, which will be sent to the model for processing.

System Prompt: A set of instructions guiding the model on how to behave while responding. For example, it can instruct the model to avoid certain actions or to follow specific response formats.

No-op: When activated, this option prevents any operation (or model call) from occurring, meaning the model won't be triggered, useful when a response is unnecessary.

Respond Without Calling: If enabled, this generates a response based on pre-existing conditions or information without actively querying the language model.

Fallback Outputs: Specifies a backup response in case the model call fails or doesn’t return valid output.

This node is typically used to trigger LLMs for real-time responses within workflows. It allows flexibility in whether to call the model or provide alternative responses based on the user's context.

hashtag
LLM (Chat)

The LLM (Chat) node is used to integrate a language model for generating conversational responses within a workflow. Here's a detailed breakdown of its key elements:

  • Label: The name of the node, which is by default set as LLM (Chat). You can rename it to something more specific based on the function of the node in your workflow.

  • Model: This field specifies the language model being used. In this case, it’s gpt-3.5-turbo-1106:chat, providing information about the model’s token limit, input cost, and output cost. The context size allows for up to 16,385 tokens, and the price for input and output tokens is displayed for budget considerations.

  • Messages: This required field captures the message history or input data sent to the model. The messages are structured with roles such as user, assistant, or system, and the model uses this context to generate appropriate responses.

  • System Prompt: The system prompt contains predefined instructions that shape how the model responds during the conversation. You can use it to direct the AI to follow certain rules or exhibit specific behavior, such as using a formal tone or sticking to specific topics.

  • Temperature: The temperature controls the randomness or creativity of the model’s output. A higher value (closer to 2) leads to more varied responses, while a lower value (closer to 0) results in more predictable, deterministic answers.

  • Presence Penalty: This parameter penalizes the model for using the same tokens or information repeatedly, encouraging it to generate new content. It’s useful for making sure responses are diverse and not repetitive.

  • Max Tokens: This field sets a limit on the number of tokens (words or word fragments) that the model can generate in its response. Setting this value helps control the length of the model’s output.

  • Top P: The Top P parameter is a sampling method that determines how diverse the responses can be. Lowering the value restricts the model to more likely words, while raising it allows for more creativity by considering a broader range of possible responses.

hashtag
Usage

The LLM (Chat) node is ideal for conversational workflows where dynamic, context-based responses are needed. It can be used in chatbot systems or in any environment where the model needs to generate text based on prior input and guidance from a system prompt. By adjusting parameters like the temperature, presence penalty, and max tokens, you can fine-tune the model’s behavior to suit specific requirements.

hashtag
Chat History

The Chat History node is designed to retrieve and manage the history of messages exchanged between the user and the AI. This is particularly useful for maintaining context in longer conversations. Here’s how the key parameters of this node work:

  • Label: The name of the node. This can be renamed to something more descriptive based on the use case.

  • User Prompt: This field is where you define the input from the user that triggers the retrieval of chat history. You can set it to filter or select specific parts of the chat history based on the user’s request.

  • Messages (object[]): This field is an output object where the list of messages (or chat history) is stored. These messages can then be used or passed to other nodes in the workflow.

  • Limit: This field allows you to specify the number of past messages to retrieve. Setting a limit can help control how much chat history is recalled, ensuring only the most relevant messages are brought forward (useful in cases of lengthy conversations).

  • Fallback Outputs: This provides an alternative output in case the node doesn’t return any valid chat history or an error occurs. This ensures continuity in the workflow.

  • Results: The final output or the list of messages retrieved is shown here, which can then be passed to subsequent nodes for further processing or decision-making.

This node is particularly useful for preserving conversation context, ensuring that the AI can respond intelligently based on previous interactions within a conversation.

Last updated