Understanding APIs

Wiresk automates Flows by interacting with the APIs of your connected applications. It does not host or expose its own APIs for this purpose. Instead, Wiresk connects to third-party apps (like Notion, Slack, or Odoo) to either fetch data or send commands using those apps’ public APIs.

This document clarifies what an API is, how Wiresk uses external APIs to power automations, and how Triggers and Methods fit into that system.

What is an API? Copy Link

An API (Application Programming Interface) is a set of rules that allows one application to interact with another. For example, APIs define how one system can request data from another, or how it can perform an action like creating or updating records.

How Wiresk Uses APIs Copy Link

Wiresk connects to external applications via their APIs to perform automation tasks.

Wiresk uses APIs in two ways:

• To detect events in external applications (via Triggers)
• To perform actions in those applications (via Methods)

You never have to write code or manually handle the API calls—Wiresk handles everything behind the scenes.

Triggers (Start the Flow) Copy Link

A Trigger defines when a Flow starts and where the first data comes from. While it may rely on APIs in the background, a Trigger is not itself an API.

There are different types of Triggers in Wiresk:

• Webhook Trigger – The external application sends data to Wiresk when an event occurs (e.g., new order, updated record).
• Scheduled Trigger – Wiresk regularly calls the API of the external application to check for updates.
• HTTP Trigger – You or an external system sends an HTTP request to Wiresk to start the Flow. This can be used for testing, one-time actions, or connecting systems that don’t support webhooks.

Methods (Steps in the Flow) Copy Link

Once a Flow starts, Methods are used to perform tasks using the APIs of external applications. Each Method corresponds to an API call, such as:

• Creating or updating a record
• Sending a message
• Fetching related data

These steps are configured visually—no coding is required.

Example:
If the Trigger pulls new records from Notion, a Method can:

• Send a message to Slack
• Then log the data in Google Sheets

Each of those is powered by the relevant application’s API.

APIs Documentations Copy Link

If you are working with a developer or setting up advanced automations, Wiresk’s documentation links directly to the official API docs for each connected application.

You’ll find:

• Supported endpoints
• Required parameters
• Expected response formats

This is helpful for understanding how the integrations work and how to pass the correct data.

Example: Automating with Notion Copy Link

Use Case:
Every morning, you want Wiresk to check Notion for new pages and log their titles in Google Sheets.

Steps:

• Trigger: Scheduled Notion Trigger that checks the database (calls Notion’s API in the background)
• Method: “Add new Row” in Google Sheets

No code. Just steps.
Wiresk handles the API logic internally while you design workflows visually.

Don’t stop here! Copy Link