FullContact × Ambacti

Bring FullContact into
the flow of work.

A little less busywork with FullContact.

Roman aqueduct developing from a precise architectural drawing into marble.
Gather contextDo the workReview & share
Multi-field-request1 capabilities
  • Get multi field request

    This endpoint allows you to make a multi field request for enriching data.

Person1 capabilities
  • Enrich person

    Lookup and enrich individuals by sending any identifiers you may already have.

Permission4 capabilities
  • Create permission

    Create an individual's current permissions state by providing one or many of the acceptable multi field inputs.

  • Delete permission

    Delete a previously permitted consumer record by providing one or many of the acceptable multi field inputs.

  • Find permission

    Find and retrieve the permission history for an individual using one or many of the acceptable multi field inputs.

  • Verify permission

    Retrieve and verify the permission state for an individual by purpose and channel.

Enrich5 capabilities
  • Obtain enrichment data

    This endpoint is used to obtain enrichment data for a specified input.

  • Run a test

    This endpoint allows you to run a test via the FullContact platform.

  • Submit a multi-field request

    This endpoint is used to submit a multi-field request for enrichment.

  • Get properties for a request

    This endpoint is used to get request properties for the enrichment process.

  • Configure webhooks

    This endpoint is used to configure webhooks for enrichment updates.

Company2 capabilities
  • Get company enrich data

    Retrieve enrichment data for a specific company.

  • Create company enrichment

    Retrieve information about a company by supplying the domain name.

Frequently asked
questions.

What could an Ambacti integration do with FullContact?

The documented operations include Multi-field-request: Get multi field request; Person: Enrich person; Permission: Create permission; Permission: Delete permission.

Could I keep a workflow read-only?

For a read-only workflow, limit account permissions to reading data and exclude actions that create, update, or delete records.

Will every action run automatically?

Choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.

Do I need to review actions in FullContact?

Decide which work could run on its own and which steps need your review.