By importing a pre-configured workflow, you can synchronize the Create Visitor and Update Visitor events from the 3Chat backend to a specified Feishu Bitable, enabling automatic addition and updating of visitor information.
Configuration Process: Import Workflow → Fill in Runtime Configuration → Publish Workflow → Configure Webhook → Add Feishu App and Set Table Fields → Test Synchronization.
I. Import Workflow
- Open the Workflow Builder @工作流构建台 and click “Import”.
- Select the pre-configuration file and complete the import.
- Open the imported workflow to prepare for filling in the runtime configuration.
Pre-configuration File:
II. Fill in Runtime Configuration
Enter the workflow’s “Runtime Configuration” and fill in the following:
| Configuration Item | Content to Fill |
|---|---|
feishu.table_url |
The full URL of the Feishu Bitable to sync to (including the table= parameter) |
feishu.app_id |
The App ID of the Feishu App |
feishu.app_secret |
The App Secret of the Feishu App |
Note: You can obtain the App ID and App Secret from your administrator, or via relevant documentation or tutorials provided by the creator. Please keep the App Secret secure.
The workflow will automatically identify the target data table from the Bitable URL, so there is no need to separately fill in app_token or table_id. Save the runtime configuration after filling it out.
III. Publish Workflow
- Publish the workflow in the Workflow Builder.
- Record the request URL and headers provided after publishing, as they will be used for subsequent Webhook configuration.
IV. Configure Webhook in 3Chat Backend
- Go to 3Chat Backend → Webhook and create one Webhook listening task.
- In the same task, select both the “Create Visitor” and “Update Visitor” events.
- Set the task’s Request URL to the request address obtained after publishing the workflow in Step III, ensuring that both events are sent to the same request URL.
- After completing the header configuration, save the Webhook task.

Webhook Header Configuration (External Network)
{
"X-Tenant-Id": [
"{From the published workflow}"
],
"Authorization": [
"Bearer {Create a permanent token at @https://app.3chatai.cn/user-hub/multiview/core_openapi_app and fill it in here}"
]
}
Webhook Header Configuration (Internal Network)
Request URL: Replace https://app.3chatai.cn with http://workflow-builder-api-svc:8080
{
"X-Tenant-Id": [
"{From the published workflow}"
]
}
V. Add App to Feishu Bitable
- Open the Feishu Bitable where you want to receive visitor information.
- Add an app to this Bitable.
- Configure admin permissions for this app.
App Name:
base_table_data_processing

VI. Configure Feishu Bitable Fields
The workflow automatically matches fields by field name: The column names in the Feishu Bitable must match the API field names in the Webhook exactly (case-sensitive); fields without matching names will be skipped.
You can refer to the following example to create the columns to be synchronized:
| Field Name | Purpose |
|---|---|
id |
Visitor Business ID |
accountId |
Visitor Account ID |
name |
Visitor Name |
totalVisits |
Number of Visits |
has_spoken_c |
Has Spoken? |
has_left_contact_c |
Left Contact Info? |
Important: At least one of
idoraccountIdmust be configured. When updating a visitor, the workflow first looks up the original record based ondata.id; ifidis unavailable or not found, it then looks up based ondata.accountId. Therefore, the Feishu table needs at least one corresponding lookup field, and the event data should provide a non-empty value for that field. It is recommended to keep both fields and avoid duplicate lookup values.
Field Synchronization Principle: The workflow reads the first-level fields under data and the first-level fields under extendMap from the Webhook, matches them with columns of the same name in the Feishu table, and writes them. For creating visitors, new records are added; for updating visitors, existing records are located and updated.
Test Synchronization: After completing the configuration, use the sandbox to test once each for “Create Visitor” and “Update Visitor” to confirm that the Feishu Bitable can add visitors and update information on existing records.


