Fulcrum

The Fulcrum digital data collection platform eliminates the inconsistencies of pen and paper, the expense of in-house platforms, and the delays caused by IT's backlog.

Power end-to-end data operations for your Fulcrum API with Nexla. Our bi-directional Fulcrum connector is purpose-built for Fulcrum, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Fulcrum or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Fulcrum workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Fulcrum credential, you need to obtain an API token from your Fulcrum account. The API token is required to authenticate with the Fulcrum API.

To obtain your API token, you need to have a Fulcrum account with API access enabled. Once you have access to your account, you can generate an API token from your Fulcrum account settings. The API token is sent in the X-ApiToken header for all API requests to the Fulcrum API. For detailed information about API token setup and authentication, refer to the Fulcrum API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key Value	Yes	Yes

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Fulcrum

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Fulcrum API token in the API Key Value field. This is the API token you obtained from your Fulcrum account settings. The API token is sent in the X-ApiToken header for all API requests to the Fulcrum API.

   Keep your API token secure and do not share it publicly. The API token provides access to your Fulcrum account and should be treated as sensitive information. You can view and manage your API tokens in your Fulcrum account settings. For detailed information about obtaining and managing API tokens, see the Fulcrum API documentation.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Fulcrum connector tile, then select the credential that will be used to connect to the Fulcrum instance, and click Next; or, create a new Fulcrum credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Fulcrum endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Records get all

Retrieve all records from your Fulcrum account.

• This endpoint automatically retrieves all records from your Fulcrum account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses GET requests to https://api.fulcrumapp.com/api/v2/records.json. The endpoint URL is automatically constructed based on the Fulcrum API base URL.
• The endpoint uses incrementing pagination, automatically fetching additional pages as needed. Pagination starts from page 1 and increments by 1 for each subsequent page. Nexla will continue fetching pages until all records are retrieved.
• The endpoint will return all records in your Fulcrum account. The response data is extracted from the records array in the API response ($.records[*]), with each record processed individually.

This endpoint retrieves all records from your Fulcrum account. Records represent data entries collected through your Fulcrum forms. The endpoint uses incrementing pagination (iteration.type: paging.incrementing) starting from page 1. The response data path is $.records[*], which extracts all items from the records array in the API response. For detailed information about retrieving records, see the Fulcrum API documentation.

Get all projects

Retrieve all projects from your Fulcrum account.

• This endpoint automatically retrieves all projects from your Fulcrum account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses GET requests to https://api.fulcrumapp.com/api/v2/projects.json. The endpoint URL is automatically constructed based on the Fulcrum API base URL.
• The endpoint uses incrementing pagination, automatically fetching additional pages as needed. Pagination starts from page 1 and increments by 1 for each subsequent page. Nexla will continue fetching pages until all projects are retrieved.
• The endpoint will return all projects in your Fulcrum account. The response data is extracted from the projects array in the API response ($.projects[*]), with each project processed individually.

This endpoint retrieves all projects from your Fulcrum account. Projects are containers for forms and records in Fulcrum. The endpoint uses incrementing pagination (iteration.type: paging.incrementing) starting from page 1. The response data path is $.projects[*], which extracts all items from the projects array in the API response. For detailed information about retrieving projects, see the Fulcrum API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Fulcrum data sources can also be manually configured to ingest data from any valid Fulcrum API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Fulcrum API endpoints typically follow the pattern https://api.fulcrumapp.com/api/v2/{endpoint_path}. The endpoint requires API Token authentication via the X-ApiToken header, which is handled automatically by your credential configuration. For detailed information about Fulcrum API endpoints and available APIs, see the Fulcrum API documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Fulcrum data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Fulcrum destination, and select the Send to Destination option from the menu. Select the Fulcrum connector from the list of available destination connectors, then select the credential that will be used to connect to the Fulcrum organization, and click Next; or, create a new Fulcrum credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Fulcrum endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Record

Create a new record in your Fulcrum account.

• This endpoint automatically creates a new record in your Fulcrum account using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses POST requests to https://api.fulcrumapp.com/api/v2/records.json. The endpoint URL is automatically constructed based on the Fulcrum API base URL.
• The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the record data to create.
• Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create a record. If you need to create multiple records, you can send multiple records, but each will be processed as a separate request.
• This endpoint does not automatically create a data source to track the responses received from the Fulcrum API after each call.

The request body must be properly formatted JSON that matches the Fulcrum API specification for creating records. The endpoint requires API Token authentication via the X-ApiToken header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about creating records, including required fields, field names, and request formats, see the Fulcrum API documentation.

Create Project

Create a new project in your Fulcrum account.

• This endpoint automatically creates a new project in your Fulcrum account using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses POST requests to https://api.fulcrumapp.com/api/v2/projects.json. The endpoint URL is automatically constructed based on the Fulcrum API base URL.
• The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the project data to create.
• Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create a project. If you need to create multiple projects, you can send multiple records, but each will be processed as a separate request.
• This endpoint does not automatically create a data source to track the responses received from the Fulcrum API after each call.

The request body must be properly formatted JSON that matches the Fulcrum API specification for creating projects. The endpoint requires API Token authentication via the X-ApiToken header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about creating projects, including required fields, field names, and request formats, see the Fulcrum API documentation.

Manual configuration

Fulcrum destinations can also be manually configured to send data to any valid Fulcrum API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Fulcrum API endpoints typically follow the pattern https://api.fulcrumapp.com/api/v2/{endpoint_path}. The endpoint requires API Token authentication via the X-ApiToken header, which is handled automatically by your credential configuration. For update/upsert operations, include the ID of the object to be updated at the end of the URL. For detailed information about Fulcrum API endpoints and available APIs, see the Fulcrum API documentation.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Fulcrum endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Fulcrum endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.