Skip to main content
SentiLink Match completes one missing identity field for an individual applicant. The Workflow Builder block exposes two services:
SentiLink Match is a bring-your-own-credentials service. Your organization must connect a SentiLink account and token before either completion service can run.

Requirements

Both services validate the current application data before calling SentiLink.

SSN Completion

DOB Completion

The previous combinations that omitted the street address or ZIP code are no longer valid. The current request validator requires the full name and address fields for both operations.

Run through the application enrichment API

  1. Call PUT /api/applications/{application_id}/enrich through Enrich Business Credit Application.
  2. Set provider to sentilink_ssn_completion or sentilink_dob_completion.
  3. Do not send service-specific options; neither service requires options.
  4. Include stage_id only when the application workflow requires a specific underwriting stage.
  5. Confirm that the response contains data.onqueue: true.
  6. Poll Get Commercial Data with the applicable services[] filter.
The request is asynchronous. data.onqueue: true confirms that Lendflow queued the job; it does not mean SentiLink returned a completed value.
The result or stored request can contain an SSN. Restrict access, avoid logging these objects, and mask sensitive values in your interface.

Data Orchestration availability and flow

The Sentilink Match block is available in Workflow Builder’s underwriting Match group for individual entities. It contains both completion services and has no provider-specific options.
  1. Add Sentilink Match to an individual underwriting workflow.
  2. Ensure the required application fields and SentiLink credentials are available before the block runs.
  3. Connect the block in the required execution order, then save and publish the workflow.
  4. Execute the published orchestration through Execute Data Orchestration with template_id, application_id, and stage_id when applicable.
  5. Confirm that the response contains data.executed: true.
  6. Monitor the asynchronous run with List Data Orchestration Logs.
  7. Read each service’s status and result from the commercial-data paths above.
The block does not require another data-service block to run first. Its dependency is complete individual identity data: DOB Completion needs an SSN, while SSN Completion can use a DOB when one is available.

What the service returns

Representative response

This abbreviated response is based on Lendflow’s current SentiLink completion fixtures. Identifiers and personal data are sanitized.

Response attributes

Completed identity data

Execution metadata

Errors and statuses

FAQ

No. The current validator requires address line 1, city, state, and ZIP code for both completion services.
No. It only confirms that the job was queued. Poll the commercial-data endpoint, wait for Success, and inspect updated_fields.
The field is optional. Lendflow’s current DOB Completion fixture omits it, and integrations must handle an absent value.