Operator | Notion

This document describes how to use Transfer, Response, and Context blocks.

Index

▶ Plan Control

The access rights to Operator > Async Block are controlled by your subcribe plan.
If you use an Async Block that does not include a fee, a caution message will appear when saving. (There are unavailable blocks included. Please check and try again.)

	Free	Starter	Plus	Pro	Enterprise
**Protocol

Async** | - | - | - | ✓ | ✓ |

▶ Restful Block

Restful blocks provide the most commonly used Transfer blocksets as a single block.
- Transfer + Protocol + Https + Response Context

기능	설명	비고
ID	The unique ID of the Transfer blockset is automatically created when the block is registered.
method	The http(s) method to call the API. Applicable options are post, get, put, delete, patch.
end-point	The endpoint (address) of the API to call.
header	Header area of data to request to the server.
body	Body area of data to request to server.
options	Used when you need additional options for API calls	Option information

▶ Transfer Blockset

Transfer blocksets are used by servers (services) to request data requests and commands through specific Protocols or to process responses.

Untitled

Function	Explanation
ID	The unique ID of the Transfer blockset is automatically created when the block is registered.
protocol unit	Enter the protocol blockset of the API to be called.
contexts	Define the response object to be received after executing the API as a Response Context block.

▶ Async

This is an Adapter Block for Async processing.
SyncTree is based on the ‘synchronous processing’ method, which is performed step by step from the top.