Application Nodes

5. Application Nodes

Application nodes allow SkyStudio workflows to connect to external applications and services.

These nodes can be used to perform email and calendar operations, access files and documents, work with messaging and collaboration platforms, interact with project management and CRM systems, process meeting records, and incorporate software development processes into workflows.

Most application nodes require an Application Connection to be created for the relevant service before they can be used.

The general usage process is as follows:

1. Use Add Node from the workflow workspace.
2. Select the application node you want to use.
3. Select the operation the node will perform.
4. If required, create an Application Connection for the relevant service.
5. Select the connection you created from the Application Connections field in the node's right-hand panel.
6. Configure the required parameters for the selected operation.
7. To use outputs from previous nodes, enter the / character in the relevant parameter field.
8. After completing the configuration, run the node using Test to verify that the connection and parameters work correctly.

---

5.1. Outlook​

The Outlook node allows SkyStudio workflows to work with a Microsoft Outlook email account.

This node can be used to send emails and perform advanced search and filtering operations in the Outlook inbox.

Connection Setup and Management​

The Outlook node uses Microsoft's OAuth 2.0 authorization method. You do not need to provide an API key or manually enter a token.

To create the connection directly from the node:

1. Add the Outlook node to the workflow.
2. Click the node to open the right-hand configuration panel.
3. Select either the Send Mail or Search Mail operation.
4. Click Connect to Microsoft Outlook.
5. Sign in with your corporate or personal Microsoft account on the Microsoft sign-in screen.
6. Approve the requested permissions to allow SkyStudio to access the Outlook account.
7. Once authorization is complete, the connection becomes active.

The connection can also be created from the Application Connections screen:

1. Go to Application Connections from the SkyStudio left-hand menu.
2. Click Add New Connection.
3. Select Microsoft Outlook as the provider.
4. Enter a descriptive name in the Connection Name field.
5. Select Authorize with Microsoft.
6. Complete the Microsoft sign-in and permission steps.
7. Once authorization is complete, the connection is saved automatically.

OAuth authorization is performed through Microsoft's official sign-in screen. SkyStudio does not see or store your Microsoft account password.

Assigning the Connection to the Node​

After adding the Outlook node to the workspace, select the connection you created from the Application Connections field in the right-hand panel.

You can create separate connections for personal and corporate Outlook accounts.

Operations​

The Outlook node provides two operations:

Operation	Description
Send Mail	Creates and sends a new email through Outlook.
Search Mail	Performs search and filtering in the Outlook inbox.

Send Mail​

Sends an email through the connected Microsoft Outlook account.

Main parameters:

Parameter	Required	Description
Connection	Yes	Outlook connection to use
To	Yes	Recipient email address
Subject	Yes	Email subject line
Body	Yes	Email content
CC	No	Addresses to include as CC recipients
BCC	No	Addresses to include as BCC recipients

If multiple recipients are used, email addresses can be separated by commas.

Text generated by previous nodes can be connected to the Body field by using /.

Search Mail​

Searches the Outlook inbox using criteria such as keyword, sender, or subject.

Main parameters:

Parameter	Required	Description
Connection	Yes	Outlook connection to use
Search Query	Yes	Search query
Folder	No	Folder to search
Limit	No	Maximum number of emails to return

Example search queries:

• invoice
• from:ahmet@company.com
• subject:meeting
• hasAttachment:true

---

5.2. Outlook Calendar​

The Outlook Calendar node allows SkyStudio workflows to work with Microsoft Outlook Calendar.

This node can be used to list, create, update, and delete events. It can also check user availability and query calendar data using natural language.

Connection Setup and Management​

Outlook Calendar can be used with two different connection methods:

• OAuth 2.0
• Azure App Registration

To create a connection with OAuth 2.0:

1. Go to Application Connections.
2. Click Add New Connection.
3. Select Outlook Calendar as the provider.
4. Select OAuth 2.0 as the connection method.
5. Specify who can use the connection in workflows.
6. Click Connect Calendar with Microsoft.
7. Sign in with your Microsoft account.
8. Approve the requested calendar access permissions.

Creating an Azure App Registration​

Azure App Registration can be used for corporate connections.

1. Sign in to Azure Portal.
2. Go to App registrations.
3. Click New registration.
4. Enter a descriptive name for the application.
5. Select Single tenant as the account type.
6. Create the application.
7. Copy the Application (client) ID.
8. Copy the Directory (tenant) ID.
9. Go to Certificates & secrets.
10. Create a Client Secret using New client secret.
11. Immediately copy the Value of the generated secret.

The Client Secret value is displayed in full only when it is first created.

API Permissions​

The required permissions for Outlook Calendar operations must be configured in Microsoft Graph.

Permission	Description
Calendars.Read	Read calendar events
Calendars.ReadWrite	Create, update, and delete events
User.Read.All	Access user and availability information

After adding the permissions, Grant admin consent may be required.

Adding the Connection to SkyStudio​

When using the Azure method, enter the following information:

• Connection Name
• Tenant ID
• Client ID
• Client Secret
• User Email

After saving the connection, select it from the Application Connections field of the Outlook Calendar node.

Operations​

Outlook Calendar provides the following operations:

• Get Events
• Today's Events
• Upcoming Events
• Check Availability
• Outlook Calendar AI Assistant
• List Calendars
• Get Event
• Create Event
• Update Event
• Delete Event

Create Event​

The following information can be used when creating a new calendar event:

• Calendar ID
• Subject
• Body
• Start Date Time
• End Date Time
• Timezone
• Location
• Attendees
• Teams Meeting
• All Day Event

Date and time values are entered in YYYY-MM-DDTHH:MM:SS format.

For Türkiye, the Timezone value can be set to Europe/Istanbul.

When Teams Meeting is enabled, a Teams meeting link can be added automatically. The required Online Meetings permissions must be configured on the App Registration.

Check Availability​

The availability of one or more users can be checked for a specified time range.

Multiple email addresses can be entered by separating them with commas.

Common Errors​

• 401 Unauthorized: The Client Secret may have expired.
• 403 Forbidden: The Calendars.ReadWrite permission may be missing.
• Event not found: The Event ID may be incorrect.
• Invalid datetime format: Check the date format.
• Empty event list: Check the Calendar ID or date range.

---

5.3. Google Calendar​

The Google Calendar node allows SkyStudio workflows to work with Google Calendar.

Events can be read, created, updated, and deleted. Calendar data can also be queried using natural language.

Connection Setup and Management​

1. Go to Application Connections from the SkyStudio left-hand menu.
2. Click Add New Connection.
3. Select Google Calendar as the provider.
4. Click Authorize with Google.
5. Select the account you want to use on the Google OAuth screen.
6. Approve the requested access permissions.
7. Once authorization is complete, the connection is saved automatically.

Google Calendar uses OAuth 2.0. Your Google account password is not shared with SkyStudio.

Assigning the Connection to the Node​

After adding the Google Calendar node to the workspace, select the Google connection you created from the Application Connections field in the right-hand panel.

Calendar ID​

Calendar ID determines which calendar the operation will be performed on.

Value	Description
primary	The user's default calendar
User email address	A specific calendar
Custom ID	Unique identifier generated by Google Calendar

The Calendar ID can be found in Google Calendar under Calendar Settings → Integrate calendar → Calendar ID.

Operations​

Google Calendar provides nine operations:

• Get Events
• Today's Events
• Upcoming Events
• Google Calendar AI Assistant
• List Calendars
• Get Event
• Create Event
• Update Event
• Delete Event

Create Event​

Main parameters:

• Connection
• Calendar ID
• Title
• Description
• Start Date Time
• End Date Time
• Timezone
• Location
• Attendees
• All Day Event

Multiple attendees can be added as comma-separated email addresses.

Usage Notes​

Date and time values should use the YYYY-MM-DDTHH:MM:SS format.

Timezone is configured as a separate parameter.

For Türkiye, Europe/Istanbul can be used.

Update Event changes only the specified fields.

Delete Event is a permanent operation.

---

5.4. Google Drive​

The Google Drive node allows SkyStudio workflows to work with Google Drive and Google Sheets.

It can be used for file search, file reading, folder management, and spreadsheet operations.

Connection Setup and Management​

The recommended connection method is OAuth 2.0.

1. Open Application Connections.
2. Select the Google Drive provider.
3. Make sure the connection method is OAuth 2.0.
4. Enter a descriptive name for the connection.
5. Click Authorize with Google.
6. Select your Google account.
7. Approve the requested permissions for Drive and Sheets access.
8. Once authorization is complete, the connection is saved.

For advanced use cases, Google Cloud credentials can also be defined manually in JSON format.

Operations​

Google Drive provides 13 operations:

• List Files
• Search Files
• Google Drive AI Assistant
• Get Spreadsheet Rows
• Read File Content
• Ask File
• Get File Information
• Create Folder
• Spreadsheet Information
• Add Row
• Update Cell
• Clear Cells
• Create Spreadsheet

List Files​

Lists files and folders within a specified folder.

If Folder ID is left empty, the root directory of Drive is used.

The Folder ID is the value after /folders/ in the Google Drive folder URL.

Get Spreadsheet Rows​

Retrieves rows from a specified cell range in Google Sheets.

Range examples:

• Sheet1
• Sheet1!A1:D50
• Sheet1!A:A
• Sheet1!1:10

The Spreadsheet ID is the value between /d/ and /edit in the Google Sheets URL.

Read File Content​

Reads the content of a file stored in Google Drive.

Text-based content such as Google Docs, Google Sheets, Google Slides, PDF, TXT, and DOCX can be used.

If AI analysis is required, analysis instructions and response language can also be specified.

Ask File​

Allows you to ask natural-language questions about the content of a specific Google Drive file.

Google Sheets Operations​

Add Row adds a new row to an existing Sheet.

Update Cell changes values within the specified Range.

Clear Cells removes cell contents while preserving formatting.

Create Spreadsheet creates a new Google Sheets file.

Common Errors​

• 401 Unauthorized: Reauthorize the Google account.
• 403 Forbidden: Check file sharing permissions.
• 404 File not found: Check the File ID or Spreadsheet ID.
• Invalid range: Check the Range format.
• Quota exceeded: The Google API quota may have been exceeded.

---

5.5. SharePoint​

The SharePoint node allows SkyStudio workflows to access lists, files, and pages in SharePoint sites.

Connection Setup and Management​

SharePoint can be connected using two methods:

• OAuth 2.0
• Azure App Registration

For OAuth 2.0:

1. Open Application Connections.
2. Click Add New Connection.
3. Select SharePoint as the provider.
4. Select the OAuth 2.0 method.
5. Specify who can use the connection.
6. Click Connect SharePoint with Microsoft.
7. Sign in with your Microsoft account.
8. Approve the requested access permissions.

Azure App Registration​

For corporate connections, the following information is used:

• Tenant ID
• Client ID
• Client Secret
• Site URL

Required Microsoft Graph permissions:

• Sites.Read.All
• Sites.ReadWrite.All
• Files.Read.All
• Files.ReadWrite.All

After configuring the permissions, Grant admin consent may be required.

Operations​

SharePoint provides 11 operations:

• Get List Items
• List Files
• Search
• SharePoint AI Assistant
• List Sites
• Get List Item
• Create List Item
• Update List Item
• Download / Read File
• Upload File
• Read Page Content

List Operations​

List data can be filtered using OData expressions.

For example:

• Status eq 'Completed'
• Priority eq 'High'
• contains(Title, 'project')

Fields can be defined in JSON format when creating and updating list items.

File Operations​

Item ID or File Path can be used for file reading operations.

For file upload operations, Library Name, Folder Path, File Name, and Content are defined.

Usage Notes​

Separate connections can be used for different SharePoint sites.

List names may be case-sensitive.

OData queries may require the SharePoint internal name values of fields.

---

5.6. Microsoft Teams​

The Microsoft Teams node allows messaging, meeting, user, and file operations in Teams to be used within workflows.

Connection Setup and Management​

Teams can be connected using OAuth 2.0 or Azure App Registration.

For OAuth 2.0:

1. Go to Application Connections.
2. Click Add New Connection.
3. Select the Microsoft Teams provider.
4. Select the OAuth 2.0 method.
5. Click Connect Teams with Microsoft.
6. Sign in with your Microsoft account.
7. Approve the requested permissions.

Azure App Registration​

1. Create an App Registration in Azure Portal.
2. Obtain the Client ID and Tenant ID values.
3. Create a Client Secret.
4. Add the required Microsoft Graph permissions.
5. Grant Admin Consent when required.
6. Enter the information into the SkyStudio connection.

API Permissions​

The source documentation lists the following permissions for Teams:

• Team.ReadBasic.All
• Channel.ReadBasic.All
• ChannelMessage.Read.All
• ChannelMessage.Send
• Chat.ReadWrite.All
• OnlineMeetings.ReadWrite.All
• Files.ReadWrite.All
• User.Read.All

Operations​

Microsoft Teams provides 12 operations:

• List Channels
• Read Channel Messages
• Send Message to Channel
• Send Chat Message
• Create Meeting
• Teams AI Assistant
• List Teams
• List Chats
• User Information
• List Users
• Send File
• Meeting Recordings

Send Message to Channel​

The main information used is Team ID, Channel ID, and Message.

The message type can be text or HTML.

Create Meeting​

The following fields can be used when creating a meeting:

• Meeting Title
• Start
• End
• Timezone
• Attendees

Common Errors​

• 401 Unauthorized: Check the Client Secret.
• 403 Forbidden: Check the Graph API permissions.
• Team/Channel not found: The Team ID or Channel ID may be incorrect.
• AADSTS700016: Check the Client ID.

---

5.7. Slack​

The Slack node allows SkyStudio workflows to work with a Slack workspace.

It can send messages to channels, read message history, search within the workspace, and retrieve user and channel information.

Creating a Slack App​

1. Open the Slack API Apps screen.
2. Click Create New App.
3. Select From scratch.
4. Enter a name for the application.
5. Select the Slack workspace to use.
6. Open OAuth & Permissions.

Bot Token Scopes​

Depending on the operations to be used, the following scopes can be added:

Scope	Usage
chat:write	Send messages
channels:history	Read channel messages
channels:read	List channels
groups:read	View private channels
users:read	List users
search:read	Search messages

After adding the scopes:

1. Click Install to Workspace.
2. Approve the permissions.
3. Copy the generated Bot User OAuth Token.

The Bot Token must begin with xoxb-.

Adding the Bot to a Channel​

The bot can operate only in channels it has joined.

In the relevant channel, use:

/invite @application_name

SkyStudio Connection​

1. Open Application Connections.
2. Create a New Connection.
3. Select Slack as the provider.
4. Define the connection name and access level.
5. Add the Bot Token beginning with xoxb-.
6. Save the connection.

Operations​

Slack provides seven operations:

• Get Channel Messages
• Send Message
• Search Messages
• Slack AI Assistant
• List Channels
• Get Channel Members
• List Users

Send Message​

The Channel field can contain a channel name, channel ID, or user ID.

To reply within a thread, use Thread TS.

For rich messages, Slack Block Kit JSON can be added to the Blocks field.

Common Errors​

• not_in_channel: Add the bot to the channel.
• channel_not_found: Check the Channel ID.
• invalid_auth: Check the Bot Token.
• missing_scope: Add the required scope.
• ratelimited: Reduce request frequency.
• not_allowed_token_type: Use an xoxb- Bot Token.

---

5.8. Jira​

The Jira node allows issue, project, board, sprint, comment, and worklog operations from Jira projects to be used in SkyStudio workflows.

Connection Setup and Management​

1. Open the Application Connections screen.
2. Click New Connection.
3. Select Jira as the provider.
4. Enter the connection information.

Main information:

Field	Description
Connection Name	A descriptive name such as Prod Jira or Test Jira
Jira Cloud Domain	yourcompany.atlassian.net
Email	Email address of your Atlassian account
API Token	Atlassian API Token

Creating an API Token​

1. Sign in to your Atlassian account.
2. Go to Account Settings / Manage Account.
3. Open the Security tab.
4. Go to API Tokens.
5. Click Create API Token.
6. Enter a descriptive name for the token.
7. Define its expiration period.
8. Create the token.
9. Copy the generated token immediately.

The token should be stored securely because it may not be displayed in full again later.

Assigning the Connection to the Node​

After adding the Jira node to the workspace, select the Jira connection you created from the Application Connections field.

The same connection can be used in multiple workflows.

Operations​

Jira provides 14 operations:

• Get Issue
• Search Issues (JQL)
• Jira AI Assistant
• Create Issue
• Change Issue Status
• Get Issue Transitions
• List Projects
• Get Project
• List Boards
• Get Sprint Issues
• Get Comments
• Add Comment
• Get Worklogs
• Add Worklog

Search Issues (JQL)​

Issues can be filtered using JQL.

Examples:

• project = ENG AND status = "To Do"
• assignee = currentUser() AND sprint in openSprints()
• project = BUGS AND priority = High AND created >= -7d
• labels = "backend" ORDER BY created DESC

Create Issue​

Main fields:

• Project Key
• Summary
• Issue Type
• Description
• Assignee Account ID
• Priority
• Labels

Issue Type can be a value defined in Jira, such as Bug, Task, Story, or Epic.

Change Issue Status​

A Transition ID is required to change the status of an issue.

If the Transition ID is unknown, first run the Get Issue Transitions operation.

Add Worklog​

Main parameters:

• Issue Key
• Time Spent
• Comment
• Started At

Time Spent examples:

• 2h 30m
• 1d
• 45m

Common Errors​

• 404 Issue not found: Check the Issue Key.
• 400 Invalid JQL: Check the JQL query.
• 403 Forbidden: Check the user's project permissions.
• Transition not found: List the valid Transition IDs again.

---

5.9. Confluence​

The Confluence node allows SkyStudio workflows to work with Atlassian Confluence content.

Confluence spaces, pages, child pages, blog content, and page history can be used in workflows.

Connection Setup and Management​

1. Go to Application Connections.
2. Click Add New Connection.
3. Select Confluence as the provider.
4. Enter the following information:

• Connection Name
• Confluence Cloud Domain
• Atlassian Email Address
• API Token

Example Cloud domain:

mycompany.atlassian.net

Creating an API Token​

1. Open the Security/API Token section of your Atlassian account.
2. Click Create API Token.
3. Enter a descriptive label for the token.
4. Create the token.
5. Immediately copy the value and add it to the SkyStudio connection.

Assigning the Connection to the Node​

After adding the Confluence node to the workspace, select the connection you created from the Application Connections field.

Operations​

Confluence provides seven operations:

• List Spaces
• Confluence AI Assistant
• List Pages
• Get Page Content
• Get Child Pages
• Get Page History
• Get Blog Pages

List Pages​

Lists pages within a specified Confluence Space.

Available fields include:

• Space Key
• Expand Fields
• Get All
• Limit
• File Path

Get Page Content​

The content of a specific page can be retrieved using the Page ID.

Body Format options:

• storage
• view
• export_view

The Page ID is the numeric value after /pages/ in the Confluence page URL.

Usage Notes​

This connection structure is designed for Confluence Cloud / Atlassian Cloud.

The Confluence Server API structure may differ.

For large pages, filtering or shortening the content before sending it to an LLM may be recommended.

---

5.10. Notion​

The Notion node allows SkyStudio workflows to work with a Notion workspace.

Pages and database records can be read, new pages can be created, content can be added to existing pages, and Notion data can be queried using natural language.

Creating an Internal Integration​

1. Open the Notion Integration management screen.
2. Create a new Internal Integration.
3. Enter a descriptive name for the integration.
4. Select the workspace to use.
5. Create the integration.
6. Copy the generated Internal Integration Token.

Page and Database Access​

Creating the token alone is not sufficient.

Pages and databases that the integration needs to access must be shared with the relevant integration.

Resources that have not been shared cannot be accessed by SkyStudio.

Adding the Connection to SkyStudio​

1. Go to Application Connections.
2. Create a new Notion connection.
3. Enter the Internal Integration Token.
4. Save the connection.
5. Select the connection from the Application Connections field of the Notion node.

Use Cases​

The Notion node can be used for:

• Listing pages
• Retrieving page information
• Reading page content
• Listing databases
• Creating new pages
• Adding content to pages
• AI-assisted Notion queries

Usage Notes​

If the parent type is set to database when creating a page, the content is created as a record within the database.

If the parent type is set to page, a child page is created under the existing page.

---

5.11. HubSpot​

The HubSpot node allows SkyStudio workflows to work with HubSpot CRM data.

Contact, company, and deal records can be queried and CRM data can be used within workflows.

Creating a Private App​

1. Sign in to your HubSpot account.
2. Go to Settings.
3. Open Integrations → Private Apps.
4. Create a new Private App.
5. Enter a descriptive name for the application.
6. Add the required scopes for the CRM data to be used.
7. Create the application.
8. Copy the generated Access Token.

For example, the relevant CRM read scopes must be configured to read contacts, deals, and companies.

Adding the Connection to SkyStudio​

1. Open Application Connections in SkyStudio.
2. Create a New Connection.
3. Select HubSpot as the provider.
4. Enter a descriptive name for the connection.
5. Add the Private App Access Token.
6. Save the connection.

Separate connections can be created for different HubSpot portals.

Assigning the Connection to the Node​

After adding the HubSpot node to the workspace, select the connection from the Application Connections field in the right-hand panel.

Use Cases​

The HubSpot node can be used especially for:

• Contact records
• Company records
• Deal records
• CRM filters
• AI-assisted CRM queries

Usage Notes​

It is recommended to explicitly specify the required property fields.

Automatic pagination can increase processing time for very large CRM datasets. Use Limit when required.

If the Private App Token changes, the SkyStudio connection must also be updated.

---

5.12. Fireflies​

The Fireflies node allows SkyStudio workflows to work with the Fireflies.ai meeting recording and transcription platform.

Meeting transcripts, summaries, and action items can be accessed, transcripts can be searched, and audio files can be processed where supported.

Getting an API Key​

1. Sign in to your Fireflies account.
2. Go to the API section under account or integration settings.
3. Create a Fireflies API Key or view your existing API Key.
4. Copy the API Key.

Adding the Connection to SkyStudio​

1. Open Application Connections.
2. Create a New Connection.
3. Select Fireflies as the provider.
4. Add the API Key to the relevant field.
5. Save the connection.

Assigning the Connection to the Node​

After adding the Fireflies node to the workspace, select the Fireflies connection you created from the Application Connections field.

Use Cases​

The Fireflies node can be used for scenarios such as:

• Listing meetings
• Reading transcripts
• Retrieving meeting summaries
• Retrieving action items
• Searching transcripts
• Processing meeting recordings

Usage Notes​

API access may be limited depending on the Fireflies plan.

If the API Key changes, the key in the SkyStudio connection must also be updated.

---

5.13. GitHub​

The GitHub node allows SkyStudio workflows to work with GitHub repositories.

Repository, issue, pull request, commit, branch, file, GitHub Actions, and release operations can be incorporated into workflows.

Creating a Personal Access Token​

A Personal Access Token is used for the GitHub connection.

1. Sign in to your GitHub account.
2. Go to Settings from the profile menu.
3. Open Developer Settings.
4. Go to the Personal Access Token section.
5. Create a new token.
6. Configure permissions appropriate for the repositories and operations to be used.
7. Create the token.
8. Copy the generated token immediately.

OAuth or App Registration is not required.

Adding the Connection to SkyStudio​

The connection primarily uses:

• Personal Access Token
• Default Owner

You can create separate connections for different organizations.

Assigning the Connection to the Node​

After adding the GitHub node to the workspace, select the connection from the Application Connections field in the right-hand panel.

Operations​

According to the source documentation, GitHub provides 15 operations:

• List Repositories
• List Issues
• List Pull Requests
• Trigger Workflow
• GitHub AI Assistant
• Repository Details
• Create Issue
• Update Issue
• Add Comment
• List Commits
• List Branches
• Get File Content
• Create / Update File
• List Releases
• Create Release

Usage Notes​

Default Owner can be used as the default value when Owner is not specified within the operation.

Values in CSV fields such as Labels and Assignees can be entered as comma-separated values.

For example:

bug,wontfix

If the GitHub token is renewed, the SkyStudio connection must also be updated.

---

5.14. Cursor​

The Cursor node allows SkyStudio workflows to work with the Cursor AI code editor platform.

Cursor team members, usage data, spending information, and analytics data can be used in workflows.

Getting an API Key​

1. Open the Cursor application or account management screen.
2. Go to the API Key section.
3. Create a new API Key.
4. Copy the key.

Adding the Connection to SkyStudio​

1. Open Application Connections.
2. Create a New Connection.
3. Select Cursor as the provider.
4. Add the API Key.
5. Save the connection.

Assigning the Connection to the Node​

After adding the Cursor node to the workspace, select the connection you created from the Application Connections field.

Use Cases​

The Cursor node can be used for:

• Listing team members
• Viewing usage data
• Querying spending information
• Retrieving analytics reports
• Performing natural-language queries through the Cursor AI Assistant

Usage Notes​

If a date range is not specified in usage or spending queries, a large amount of historical data may be returned.

For large teams, pagination and date filters are recommended.

If the API Key is renewed, the SkyStudio connection must also be updated.

---

5.15. Artifact​

The Artifact node is used to generate visual and interactive outputs in SkyStudio workflows.

It can create HTML pages, charts, and similar visual outputs using workflow data and provided instructions.

Connection Setup​

The Artifact node does not require an external application connection.

It can be added directly to the workspace and used without additional connection setup.

Operations​

The Artifact node provides four operations.

Highlighted operations include:

• Generate HTML Page
• Generate Chart

Generate HTML Page creates an AI-assisted HTML page using the provided prompt and data.

Generate Chart generates a chart based on the provided data and instructions.

Usage​

Outputs from previous nodes can be connected to the Artifact node as parameters.

For example, a dataset generated as the result of data analysis can be presented to the user as a visual report through the Artifact node.

Usage Notes​

Outputs generated by Artifact operations are rendered in SkyStudio's Artifact viewer component and presented interactively to the user.

---

5.16. Form Builder​

The Form Builder node creates interactive forms for collecting structured data from users in SkyStudio workflows.

When the defined condition is met, the form is displayed to the user. After the user completes the form, the responses can be used in subsequent workflow steps.

Connection Setup​

Form Builder does not require an external service connection.

The node is added directly to the workflow, and all configuration is performed from the right-hand panel.

Form Configuration​

Form Builder performs one primary operation:

Displaying a form and collecting user input

Different field types can be used within a form:

• Text
• Long Text
• Number
• Date
• Selection
• Checkbox

Use + Add Field to add a new field.

Fields can be reordered using drag and drop when required.

Form Display Condition​

The condition that determines when the form is displayed to the user can be defined in natural language.

The system evaluates this description and can trigger the form when the appropriate condition is met.

Using Form Responses​

Values entered by the user can be retrieved from the Form Builder node output and used in subsequent nodes.

This data can be passed to:

• If-Else conditions
• LLM nodes
• Jira or CRM nodes
• Messaging nodes
• Data processing steps

Usage Notes​

A unique Form ID must be defined for each Form Builder.

Multiple Form Builder nodes can be used in the same workflow, but their Form ID values must be different.

The output order of form fields follows the order in which the fields are defined in the form. If the field order is changed, index references used in subsequent nodes should also be reviewed.

To avoid reducing usability with very long forms, large forms should be divided into multiple steps.