A stack is a server or set of servers where integrator.io runs extension functions, such as hooks and wrappers. It stores references to your servers or AWS Lambda functions so integrator.io knows where to call them at runtime. Because integrator.io is a distributed system, different components can run on different servers to handle multiple operations simultaneously. This article explains how to create AWS Lambda and server stacks and how to share or restrict access to them.
You configure a stack by pointing integrator.io to your server or Lambda function, and integrator.io calls it automatically. Store your system token as the INTEGRATOR_EXTENSION_SYSTEM_TOKEN environment variable on any server where extension code runs.
Note
You must have at least Manage All permissions at the integration or account level to create or manage stacks.
integrator.io supports execution of extension functions through the following extension types:
-
Express-based app running on a server
Note
Click → to create and manage stacks.
A framework version defines how extension functions should be structured and what API calls each function is permitted to make. The framework version is visible in the Framework column on the Stacks list page.
In framework 1.0, all extension functions, regardless of type, can perform create, update, and delete operations on any resource within the integration. Functions are grouped under named categories such as hooks, settings, and uninstaller.
In framework 2.0, access depends on the type of the extension function. A hook function, for example, can only make the API calls appropriate for that hook — it cannot read or modify other parts of the integration. Functions are exposed at the top level.
All new stacks created from integrator.io default to framework 2.0. Stacks created without a framework field remain on framework 1.0. There is no automatic migration from 1.0 to 2.0.
When you edit an existing stack, the framework version remains unchanged.
-
Navigate to → .
-
Click + Create stack.
-
In the Name field, enter a name for the stack.
-
In the Type field, select AWS Lambda.
-
Enter the Access Key Id and the Secret Access Key.
-
Select the region from the AWS Region drop-down list.
-
Enter the Function name.
-
Select C#, Java, Node.js, or Other from the Language drop-down list.
-
Click Save & close.
|
Field |
Description |
|---|---|
|
Name |
The name of the stack. |
|
Type |
The type of stack. Select AWS Lambda for an AWS Lambda stack. |
|
Access Key Id |
Your AWS access key identifier. |
|
Secret Access Key |
Your AWS secret access key. |
|
AWS Region |
The region where your Lambda function is deployed. |
|
Function name |
The name of your AWS Lambda function. |
|
Language |
The runtime language of your Lambda function. Accepted values: C#, Java, Node.js, Other. |
-
Navigate to → .
-
Click + Create stack.
-
In the Name field, enter a name for the stack.
-
In the Type field, select Server.
-
Enter the server URL in the Host field.
-
Click Save & close.
|
Field |
Description |
|---|---|
|
Name |
The stack name. |
|
Type |
The type of stack. Select Server for an Express-based server stack. |
|
Host |
The URL of the server where your extension code is running. |
You can share a stack with other integrator.io users and manage their access at any time.
-
Click the Actions overflow (...) menu for the stack and select Share stack.
-
Click +Invite user.
-
Enter the email address of the integrator.io user you want to share the stack with.
-
Click Save & close.
|
Status |
Meaning |
|---|---|
|
Pending |
The user has been invited but hasn't accepted yet. |
|
Accepted |
The user has accepted the shared stack. |
Note
The invited user receives a notification with a link to accept the shared stack. Once they accept, the status updates accordingly.
Click Refresh to see the latest status of your invitation.
After the invited user accepts the shared stack, the stack is available for use.
Warning
Permanently removing a user's access deletes the share request from the system. To reshare the stack with that user, you must send a new invitation.
-
Click the Actions overflow (...) menu for the shared item and select Share stack.
-
You can use the Off/On toggle to temporarily remove a user's access from a stack. To permanently remove access, click the trash icon in the Action column next to the user whose access to the stack you want to remove.
Note
A stack is considered in use when it's referenced by a connection, import, or export. You can't remove user access from a shared stack if the stack is currently in use by that user. In such cases, an error message displays, and the share request will not be removed. You can only remove user access to a stack if the stack's reference has been removed from all connections, imports, and exports.