Integration Nodes

Integration nodes connect your workflows to external services. Send payments through Stripe, create calendar events in Google Calendar, post messages to Slack, and more. There are 12 integration nodes in total.

All integration nodes pull credentials dynamically from your Otesse settings — you do not need to paste API keys into the canvas.

API Endpoint

Icon: Globe

Make HTTP requests to any external API. Supports all standard HTTP methods and custom headers.

Inputs: data-in (request parameters)

Outputs: data-out (response data), error (if request failed)

Config:

URL: The API endpoint
Method: GET, POST, PUT, DELETE
Headers: Custom request headers
Body: Request body for POST/PUT
Authentication: Bearer token, API key, or basic auth

Example: Call a third-party property management API to sync booking data.

Webhook

Icon: Webhook

Receive incoming webhook events from external services. Otesse generates a unique URL that external services can post data to.

Inputs: None (this is a trigger node)

Outputs: data-out (webhook payload)

Config:

Secret: Optional webhook secret for verification
Expected format: JSON or form-encoded

Example: Receive a webhook from Stripe when a subscription payment succeeds or fails.

External Webhook

Icon: Send

Send outbound HTTP requests to external APIs and webhooks. Unlike API Endpoint, this is optimized for simple webhook-style notifications.

Inputs: data-in (payload to send)

Outputs: data-out (response), error (if delivery failed)

Config:

URL: Where to send the webhook
Method: POST or PUT
Headers: Custom headers
Payload: Data to send

Example: Notify a partner system when a booking status changes by posting to their webhook URL.

Stripe

Icon: CreditCard

Process payments, issue refunds, and manage customers through Stripe.

Inputs: data-in (payment or customer data)

Outputs: data-out (Stripe response), error (if operation failed)

Config:

Operation: Charge, refund, create customer, create subscription, or cancel subscription
Amount: Payment amount (for charge/refund)
Currency: Payment currency
Customer: Stripe customer ID or email

Example: After a booking is confirmed, charge the customer's card on file through Stripe.

Google Calendar

Icon: CalendarDays

Create, update, list, and delete events on Google Calendar.

Inputs: data-in (event details)

Outputs: data-out (calendar event), error (if operation failed)

Config:

Operation: Create event, update event, list events, or delete event
Calendar: Which calendar to use
Title: Event title
Start/end: Event time and duration
Attendees: Optional email addresses to invite

Example: When a booking is confirmed, create a Google Calendar event for the field crew with the customer address and service details.

Twilio

Icon: Phone

Send SMS messages, make phone calls, and look up phone numbers through Twilio.

Inputs: data-in (message or call data)

Outputs: data-out (Twilio response), error (if operation failed)

Config:

Operation: Send SMS, make call, or lookup
To: Recipient phone number
Body: Message text (for SMS)
Voice URL: TwiML URL (for calls)

Example: Send an SMS booking confirmation to the customer immediately after they book.

Postmark

Icon: Send

Send emails through Postmark — either using templates or raw HTML. Also provides delivery stats.

Inputs: data-in (email data)

Outputs: data-out (delivery status), error (if sending failed)

Config:

Operation: Send template email, send raw email, or check delivery stats
From: Sender address
To: Recipient address
Template: Postmark template ID (for template sends)
Subject/body: For raw email sends

Example: Send a beautifully formatted booking receipt using a Postmark email template.

Payout

Icon: Banknote

Trigger a payout to a worker or contractor for completed jobs.

Inputs: data-in (payout details)

Outputs: data-out (payout confirmation), error (if payout failed)

Config:

Recipient: Worker or contractor to pay
Amount: Payout amount
Method: Direct deposit, check, or other

Example: After a job is marked complete and reviewed, trigger a payout to the assigned contractor.

Slack

Icon: Hash

Send messages, create channels, and react to messages in Slack.

Inputs: data-in (message data)

Outputs: data-out (Slack response), error (if operation failed)

Config:

Operation: Send message, create channel, or add reaction
Channel: Slack channel name or ID
Message: Message text (supports Slack markdown)
Thread: Optional thread reply

Example: Post a message to the #operations channel when a high-value booking is confirmed.

Google Sheets

Icon: Table2

Read, append, and update data in Google Sheets. Useful for reporting and simple data storage.

Inputs: data-in (sheet data)

Outputs: data-out (sheet response), error (if operation failed)

Config:

Operation: Read rows, append row, update row, or create sheet
Spreadsheet: Google Sheet ID or URL
Sheet name: Which tab to use
Range: Cell range (for reads/updates)

Example: Append a new row to a daily revenue tracking spreadsheet every time a payment is processed.

QuickBooks

Icon: Receipt

Create invoices, record payments, and sync accounting data with QuickBooks.

Inputs: data-in (accounting data)

Outputs: data-out (QuickBooks response), error (if operation failed)

Config:

Operation: Create invoice, record payment, create customer, or sync
Customer: QuickBooks customer reference
Line items: Invoice line items (for create invoice)

Example: When an invoice is marked as paid in Otesse, record the payment in QuickBooks automatically.

Mapbox

Icon: Map

Geocode addresses, calculate driving routes, and check travel-time isochrones using Mapbox.

Inputs: data-in (location data)

Outputs: data-out (geographic results), error (if operation failed)

Config:

Operation: Geocode (address to coordinates), reverse geocode, directions, or isochrone
Address: Address string (for geocoding)
Origin/destination: Coordinates (for directions)
Travel time: Minutes (for isochrone)

Example: Calculate the driving distance between a worker's location and the job site to estimate arrival time.