Functions import export

Functions can be exported from one Tulip instance and imported to another using a standalone import/export workflow. Both instances must be the same version to import and export. This feature allows you to share reusable logic across different instances or workspaces.

Currently, functions must be imported and exported independently from apps. Unlike connectors and tables, apps do not carry functions during app import/export. If an app references a function and you export that app, the function will not be included, and any triggers referencing that function will display a failure message after import.

Export a function

1. Navigate to the Functions page.
2. Hover over the function you want to export and click the three-dot menu on the right side.
3. Click Export.
4. Choose to either download the export as a file or copy the export token to your clipboard.

What gets exported

When you export a Function, the following referenced items are included:

• Table definitions: The table and schema (fields and structure) only. Table data is not included.
• Connector functions: The entire Connector containing the referenced connector function.

Import a function

1. Navigate to the Functions page in the destination workspace.
2. Click the three-dot menu at the top of the page and select Import.
3. Paste the export token or upload the export file.
4. Click Import.

After import

After import, the following items appear in the target instance:

• The function appears on the Functions page.
• Referenced tables are created with their fields, but without data. You must separately export table data to a CSV and import it.
• Connectors and connector functions are imported if not already present on the destination instance. Learn more about connector and connector function import/export.

Further reading

• Functions overview
• App Import & Export