Skip to main content

Fulcrum Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a Fulcrum location.
fulcrum_api.png

Fulcrum

Create a Fulcrum Destination​

  1. Click the + icon on the Nexset that will be sent to the Fulcrum destination, and select the Send to Destination option from the menu.

  2. 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.

  3. In Nexla, Fulcrum destinations can be created using pre-built endpoint templates, which expedite destination setup for common Fulcrum endpoints. Each template is designed specifically for the corresponding Fulcrum endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Fulcrum destinations can also be configured manually, allowing you to send data to Fulcrum endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Fulcrum endpoints. Each template is designed specifically for the corresponding Fulcrum endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, 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.

Configure Manually​

Fulcrum destinations can be manually configured to send data to any valid Fulcrum API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Fulcrum destinations, such as destinations that use custom request headers, different HTTP methods, or custom data formatting.

Content Format​

  1. Select the format in which the Nexset data will be sent to the Fulcrum API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The Fulcrum API typically uses JSON format for request bodies.

API Endpoint URL​

  1. Enter the URL of the Fulcrum API endpoint to which you want to send the Nexset data in the URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Fulcrum API endpoints typically follow the pattern https://api.fulcrumapp.com/api/v2/{endpoint_path}.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. 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.