External API Nodes

Nodes for interacting with external services, making API calls, and triggering external events.

HTTP Request Node

Purpose

Make HTTP requests to external APIs or web services.

Configuration

• Method: GET, POST, PUT, DELETE, etc.
• URL: Target endpoint
• Headers: Optional request headers
• Body: Optional request payload
• Authentication: Support for various auth methods

Example

{
  "method": "GET",
  "url": "https://api.example.com/users",
  "headers": {
    "Authorization": "Bearer {{ apiToken }}"
  },
  "output": {
    "status": 200,
    "data": [{ "id": 1, "name": "John" }]
  }
}

Use Cases

• Fetch data from external services
• Submit form data
• Trigger webhooks
• Integrate third-party APIs

AI Call Node

Purpose

Invoke AI models for text generation, analysis, and processing.

Supported Models

• OpenAI GPT-4o
• OpenAI GPT-4o Mini
• Claude 3.5 Sonnet
• Claude 3.5 Haiku
• Claude 3 Opus

Configuration

• Model: Select AI provider and model
• Prompt: Input text or instructions
• Temperature: Creativity level (0-1)
• Max Tokens: Response length limit

Example

{
  "model": "claude-3.5-sonnet",
  "prompt": "Summarize the following text in three sentences:",
  "temperature": 0.7,
  "input": "Long text input...",
  "output": {
    "summary": "Concise AI-generated summary"
  }
}

Use Cases

• Text summarization
• Content generation
• Translation
• Code generation
• Sentiment analysis

Webhook Trigger Node

Purpose

Receive and process external webhook events.

Configuration

• Webhook URL: Unique endpoint
• Allowed Methods: GET, POST
• Validation: Optional security token
• Event Processing: Transform and forward webhook payload

Example

{
  "webhookUrl": "/workflows/webhooks/github-events",
  "input": {
    "repository": "user/repo",
    "event": "push"
  },
  "output": {
    "processedEvent": "Repository updated"
  }
}

Use Cases

• GitHub repository events
• Payment gateway notifications
• External system integrations

Email Node

Purpose

Send emails directly from workflows.

Configuration

• To: Recipient email(s)
• From: Sender email
• Subject: Email subject line
• Body: HTML or plain text
• Attachments: Optional file references

Example

{
  "to": ["[email protected]"],
  "subject": "Workflow Notification",
  "body": "Your workflow has completed successfully.",
  "output": {
    "status": "sent",
    "messageId": "unique-message-id"
  }
}

Use Cases

• Notifications
• Reporting
• Alerts
• User communication

Slack Message Node

Purpose

Send messages to Slack channels or direct messages.

Configuration

• Channel/User: Destination
• Message: Text or rich message
• Webhook/Bot Token: Authentication
• Formatting: Support for Slack message blocks

Example

{
  "channel": "#team-notifications",
  "message": "Workflow completed: {{ workflowName }}",
  "output": {
    "status": "sent",
    "timestamp": "2025-08-07T12:34:56Z"
  }
}

Use Cases

• Team notifications
• Workflow status updates
• Alerts and monitoring
• Team collaboration

Google Drive File Change Node

Purpose

Monitor Google Drive files for changes and trigger workflows when modifications occur.

Configuration

• Connection: Google Drive connection from vault
• File: Select specific file to monitor
• Change Detection: Automatic webhook-based monitoring

Example

{
  "connectionId": "vault-google-drive-123",
  "fileId": "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms",
  "fileName": "Spreadsheet.xlsx",
  "output": {
    "fileInfo": {
      "id": "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms",
      "name": "Spreadsheet.xlsx",
      "modifiedTime": "2024-01-15T10:30:00Z"
    },
    "triggered": true
  }
}

Use Cases

• Document approval workflows
• Automated processing when files are updated
• Collaboration triggers
• Content synchronization

Google Drive Read File Node

Purpose

Read content from Google Drive files including documents, spreadsheets, and text files.

Configuration

• Connection: Google Drive connection from vault
• File: Select file to read
• Output Format: Auto-detect, text, base64, or extracted text

Example

{
  "connectionId": "vault-google-drive-123",
  "fileId": "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms",
  "outputFormat": "auto",
  "output": {
    "content": "Document content here...",
    "fileName": "Document.docx",
    "mimeType": "application/vnd.openxmlformats-officedocument.wordprocessingml.document",
    "size": "1024",
    "format": "text"
  }
}

Use Cases

• Document processing workflows
• Content extraction and analysis
• Data import from spreadsheets
• Template processing

Google Drive Write File Node

Purpose

Write content to Google Drive files with support for appending or overwriting existing content.

Configuration

• Connection: Google Drive connection from vault
• File: Select target file to write to
• Write Mode: Choose between "append" or "overwrite"
• Input: Text content to write (from input)

Example

{
  "connectionId": "vault-google-drive-123",
  "fileId": "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms",
  "writeMode": "append",
  "input": "New content to add to the file",
  "output": {
    "fileId": "1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms",
    "fileName": "Log.txt",
    "mimeType": "text/plain",
    "writeMode": "append",
    "bytesWritten": 32,
    "modifiedTime": "2024-01-15T10:35:00Z"
  }
}

Use Cases

• Automated logging and reporting
• Content generation and updates
• Data export to Google Drive
• Workflow result documentation

Supported File Types

• Text Files: .txt, .csv, .json, .xml, .html
• Google Workspace: Docs, Sheets, Slides (converted to text)
• Write Modes:
  • Append: Add content to the end of existing file
  • Overwrite: Replace entire file content

Best Practices

• Handle rate limits
• Implement robust error handling
• Use secure authentication
• Cache and optimize API calls
• Respect third-party API guidelines
• For Google Drive: Ensure proper file permissions and connection scopes