FlutterFlow Trigger & FlutterFlow BuildShip Library

The FlutterFlow Trigger in combination with the FlutterFlow BuildShip Library provides a seamless connection between your FlutterFlow apps and BuildShip's powerful back-end workflows.

This integration enables you to leverage complex business automations set up in BuildShip directly from your FlutterFlow frontend.

This integration enables you to:

• Process data efficiently
• Integrate with external systems
• Handle enterprise-level tasks securely
• Keep sensitive business logic and operations safely abstracted from your client interface

Installation

Adding the BuildShip Library to FlutterFlow

To set up the FlutterFlow Trigger, you need to install the FlutterFlow BuildShip Library. This library is available in the FlutterFlow Marketplace and can be added to your project with just a few clicks.

• Navigate to the FlutterFlow Marketplace (opens in a new tab)
• Search for "BuildShip"
• Click on the "Trigger BuildShip Workflow" library
• Select the "Add for Free" button to make it available in your project

Configure Project Dependencies

• In FlutterFlow, go to Settings → Project Dependencies
• Under "FlutterFlow Libraries", select "Add Library"
• A configuration window will appear requesting library values

Library values are variables created by the library author but intended to have their values set by the library user. These allow configuration of settings like API keys or other library-specific configurations.

Authentication Options

BuildShip FlutterFlow Triggers offers three authentication methods depending on your project requirements:

No Authentication

No Authentication is the standard FlutterFlow trigger option that offers a simple implementation. It's ideal for testing or workflows that don't require authentication and requires no additional setup to get started.

Firebase Authentication

Firebase Authentication is recommended for apps already using Firebase Auth. This method secures your workflows with Firebase Authentication and ensures that only authorized users can trigger your backend processes.

This requires us to pass the Firebase Project ID which is used to authenticate the user and ensure they have the necessary permissions to trigger the workflow.

The authenticated user token needs to passed to the BuildShip workflow via the authorization headers, which can then be used to verify the user's identity and permissions.

Supabase Authentication

Supabase Authentication is designed for applications already using Supabase Auth. This option secures your workflows with Supabase Authentication and provides robust security for all your backend operations.

This requires the Supabase public anon key to the Integration Key input and your Supabase URL in the URL input. These values are used to authenticate the user and ensure they have the necessary permissions to trigger the workflow.

The authenticated user token needs to passed to the BuildShip workflow via the authorization headers, which can then be used to verify the user's identity and permissions.

BuildShip Trigger Setup

Setting up the connection in BuildShip is straightforward:

1. Create a new workflow or select an existing one

2. Click the Triggers button at the top of the screen. Select Add Trigger.

3. Choose the appropriate FlutterFlow Trigger from the list of available triggers.

4. Define a path in the FlutterFlow Trigger in BuildShip and click "Connect". BuildShip will automatically map the inputs defined in your workflow and generate a configuration JSON.

5. Use the copy button to capture this configuration.

Connecting FlutterFlow to BuildShip

Basic Configuration

Once you have the configuration JSON from BuildShip, you can connect it to your FlutterFlow project.

1. Return to FlutterFlow's library values screen.

2. Paste the configuration JSON into the BuildShip configuration field in library values.

⚠️

Important: This is the only field you need to configure at this stage.

Triggering BuildShip Workflows

Now you can trigger your BuildShip workflow like any other action in your project:

1. In the Action Flow Editor, locate the new action block called TriggerBuildShipWorkflow

2. Configure the remaining library values:
   • Input Values: A comma-separated list of the values your BuildShip workflow expects.
   • Format inputs as a list using code expression: ["value1", "value2", ...]

Important: Even with a single input, you must format it as a list: [input]

📘 Example: For multiple inputs, list them in the order shown in the BuildShip setup screen: [input1, input2, input3]

Authentication Setup

If using authentication, complete these additional steps:

1. Use the authOption value to select your authentication method (Firebase or Supabase)

💡

An ENUM is provided to ensure you send the correctly formatted value to BuildShip

2. Send an auth value to BuildShip for verification

   • For both Firebase and Supabase, use the JWT token of your authenticated user
   • Find this under the Authenticated User section in the options

3. Add an output value to use the response from BuildShip in subsequent actions