CRUD Integration - Synthreo Builder
CRUD Integration node for Builder - connect to external REST APIs and databases to perform create, read, update, and delete operations as steps within an AI agent workflow.
Purpose
Section titled “Purpose”The CRUD Integration node connects ThreoAI workflows to external platforms such as Monday.com, ClickUp, Airtable, and Slack. It enables automated Create, Read, Update, and Delete (CRUD) operations across business tools, ensuring seamless cross-platform workflows.
Use this node when your AI agent needs to write results back to a project management board, update records in a database, or post notifications to a messaging platform - all as part of an automated pipeline.
Inputs
Section titled “Inputs”- Workflow data that will be inserted, updated, or used in external platforms.
- Dynamic fields depend on the chosen integration type.
Outputs
Section titled “Outputs”The node returns confirmation, status, or IDs from the external system.
Output Format (example):
{ "integration_response": { "status": "success", "id": "task_123" }}Parameters
Section titled “Parameters”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
Integration Type (integrationTypeId) | Dropdown | Yes | Monday.com | Choose the target platform: Monday.com, ClickUp, Airtable, or Slack. |
Output Mode (outTransformId) | Dropdown | Yes | Original + appended result | Choose between appending integration results to the existing data row or returning only the result. |
Result Property Name (outColumnName) | Text | Yes | integration_response | Column or property name that will hold the integration results in the output data. |
Output Mode Options
Section titled “Output Mode Options”| Option | Description |
|---|---|
| Original + appended result | Keeps all upstream data and adds the integration result as a new property. Useful when downstream nodes need both input context and the integration result. |
| Result only | Returns only the integration result, discarding upstream fields. Useful when only the ID or status confirmation is needed. |
Platform-Specific Configuration
Section titled “Platform-Specific Configuration”Monday.com
Section titled “Monday.com”- Authentication: API token or OAuth 2.0.
- Configuration Fields:
| Field | Description |
|---|---|
| Board ID | The target board where items will be created or updated. |
| Group ID | The specific group (column) inside the board. |
| Item Name | Title or primary field of the new or updated item. |
| Column Values | JSON or mapped fields that set board column values. |
Common Use Cases:
- Create new leads on CRM boards when a form is submitted.
- Update project statuses automatically when an upstream node detects a change.
- Sync external system data with Monday.com boards on a schedule.
ClickUp
Section titled “ClickUp”- Authentication: API token.
- Configuration Fields:
| Field | Description |
|---|---|
| Workspace ID | The workspace to connect to. |
| List ID | The target list where tasks will be created. |
| Task Name | Name or title of the task. |
| Task Content | Description or notes for the task body. |
| Assignees | User IDs to assign the task to. |
| Due Date | Optional date field for scheduling the task. |
Common Use Cases:
- Create tasks from support tickets or form submissions.
- Update task statuses from external triggers.
- Sync project progress with ClickUp lists after a workflow completes.
Airtable
Section titled “Airtable”- Authentication: Personal access token.
- Configuration Fields:
| Field | Description |
|---|---|
| Base ID | The Airtable base to connect to. |
| Table Name | The specific table inside the base. |
| Record ID | Used for update or delete operations to identify the target record. |
| Fields Mapping | Defines which workflow fields map to Airtable column names. |
Common Use Cases:
- Add new customer records automatically when a signup workflow runs.
- Update inventory counts when orders are processed.
- Maintain synced data tables across multiple systems.
- Authentication: Slack OAuth 2.0 app with the
chat:writescope enabled. - Configuration Fields:
| Field | Description |
|---|---|
| Channel ID | The target channel where messages will be posted. |
| Message Text | The message body. Supports Slack markdown formatting. |
| Thread Timestamp | Optional. Reply to an existing thread by providing its timestamp. |
| User Mentions | Dynamically notify specific users within the message. |
Common Use Cases:
- Notify teams when new leads or tasks are created.
- Send automated alerts for critical system events detected by an AI agent.
- Post scheduled summaries or reminders to team channels.
Example Usage
Section titled “Example Usage”- Customer Support: Create ClickUp tasks automatically when support tickets are submitted through a form.
- Sales Leads: Add new leads to a Monday.com board and simultaneously notify the sales team in Slack.
- Inventory Sync: Update Airtable stock levels when e-commerce orders are processed by the workflow.
Troubleshooting
Section titled “Troubleshooting”| Issue | Likely Cause | Resolution |
|---|---|---|
| Integration returns a 401 error | API token expired or invalid | Re-enter a valid token in the authentication field. |
| Record not found on update | Incorrect Record ID passed from upstream | Verify the ID field mapping from the previous node output. |
| Slack message not posted | Bot not added to the target channel | Invite the Slack app bot to the channel before running the workflow. |
| Airtable fields not saving | Field names in mapping do not match the table schema | Open the Airtable base and verify exact column names, including capitalization. |
| ClickUp task created in wrong list | List ID points to an archived or incorrect list | Confirm the List ID from ClickUp’s URL when viewing the target list. |
Best Practices
Section titled “Best Practices”- Use descriptive result column names (for example,
clickup_task_idorslack_message_status) so downstream nodes can reference them clearly. - Choose Original + appended result when you need to carry input data alongside integration results for further processing.
- Use Result only mode when only the returned ID or status confirmation is needed by downstream steps.
- Test each integration with a single sample record before deploying to production with full data volumes.
- Ensure connected accounts have the appropriate permissions for the CRUD operations you intend to perform (for example, write access to a board or table).
- Rotate API tokens and OAuth credentials on a regular schedule and update the node configuration when you do.
Related Nodes
Section titled “Related Nodes”- HTTP Client - for calling external APIs not covered by the built-in integration types.
- Output Data - for storing or surfacing integration results to end users.
- Custom Script - for transforming or validating data before passing it to the CRUD Integration node.