Skip to main content

FullContact Data Source

Follow the instructions below to create a new data flow that ingests data from a FullContact source in Nexla.
fullcontact_api.png

FullContact

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the FullContact connector tile from the list of available connectors. Then, select the credential that will be used to connect to the FullContact instance, and click Next; or, create a new FullContact credential for use in this flow.

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

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

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common FullContact endpoints. Each template is designed specifically for the corresponding FullContact endpoint, making data source setup easy and efficient.

Endpoint Settings​

  • 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. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

    Fetch Company by Domain Name

    Fetch companies by submitting a domain name, which will then return information about the company.

    • Enter the domain name of the company you want to fetch information for in the Domain Name field. This should be a valid domain name (e.g., example.com).

    • The endpoint uses POST requests to https://api.fullcontact.com/v3/company.enrich with a JSON body containing the domain name. The endpoint URL is automatically constructed based on the FullContact API base URL.
    • The endpoint does not use pagination and returns company information in a single request.
    • The endpoint will return detailed information about the company associated with the specified domain name. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure.

    Domain names should be valid internet domain names without the protocol (e.g., example.com, not https://example.com). The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about company enrichment, see the FullContact API documentation.

    Fetch Company by Domain Name from Lookup

    Fetch companies by submitting domain names in a Nexla lookup table, which will then return information about the company.

    • Select the Nexla lookup table that contains domain names from the Lookup for fetching Domain Names dropdown menu. This lookup table should contain a column with domain names that you want to fetch company information for.

    • Enter the name of the column in the lookup table that contains the domain names in the Domain Name column name in Lookup field. This should match the exact column name in your lookup table.

    • The endpoint uses a two-step process: first, it iterates over the Nexla lookup to retrieve domain names, then it makes POST requests to https://api.fullcontact.com/v3/company.enrich with a JSON body containing the domain name for each domain from the lookup. The endpoint URL is automatically constructed based on the FullContact API base URL.
    • The endpoint does not use pagination and returns company information in a single request per domain.
    • The endpoint will return detailed information about the companies associated with each domain name found in the lookup table. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure for each company.

    This endpoint requires a Nexla lookup table containing domain names. The endpoint iterates over the lookup table and makes API requests for each domain name found in the lookup. The Domain Name column name should match the exact column name in your lookup table. Domain names should be valid internet domain names without the protocol (e.g., example.com, not https://example.com). The endpoint uses a lookup iteration (iteration.type: data.map.key.queue) followed by a static URL (iteration.type: static.url) for each lookup entry. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about company enrichment, see the FullContact API documentation.

    Fetch Person by Email

    Fetch person information by submitting an email address, which will then return information about the person.

    • Enter the email address of the person you want to fetch information for in the Email Address field. This should be a valid email address (e.g., bart@fullcontact.com).

    • The endpoint uses POST requests to https://api.fullcontact.com/v3/person.enrich with a JSON body containing the email address. The endpoint URL is automatically constructed based on the FullContact API base URL.
    • The endpoint does not use pagination and returns person information in a single request.
    • The endpoint will return detailed information about the person associated with the specified email address. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure.

    Email addresses should be valid email addresses in standard format (e.g., bart@fullcontact.com). The endpoint uses a static URL (iteration.type: static.url) and does not require pagination. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about person enrichment, see the FullContact API documentation.

    Fetch Person by Email from Lookup

    Fetch person information by submitting email addresses in a Nexla lookup table, which will then return information about the person.

    • Select the Nexla lookup table that contains email addresses from the Lookup for fetching Email Addresses dropdown menu. This lookup table should contain a column with email addresses that you want to fetch person information for.

    • Enter the name of the column in the lookup table that contains the email addresses in the Email address column name in Lookup field. This should match the exact column name in your lookup table.

    • The endpoint uses a two-step process: first, it iterates over the Nexla lookup to retrieve email addresses, then it makes POST requests to https://api.fullcontact.com/v3/person.enrich with a JSON body containing the email address for each email from the lookup. The endpoint URL is automatically constructed based on the FullContact API base URL.
    • The endpoint does not use pagination and returns person information in a single request per email.
    • The endpoint will return detailed information about the people associated with each email address found in the lookup table. The response data is extracted from the root-level object in the API response ($), and Nexla will process the entire response structure for each person.

    This endpoint requires a Nexla lookup table containing email addresses. The endpoint iterates over the lookup table and makes API requests for each email address found in the lookup. The Email address column name should match the exact column name in your lookup table. Email addresses should be valid email addresses in standard format (e.g., bart@fullcontact.com). The endpoint uses a lookup iteration (iteration.type: data.map.key.queue) followed by a static URL (iteration.type: static.url) for each lookup entry. The response data path is $, which extracts the entire root-level object from the API response. For detailed information about person enrichment, see the FullContact API documentation.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

FullContact data sources can be manually configured to ingest data from any valid FullContact 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 FullContact sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom authentication headers or request parameters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the FullContact API from the Method pulldown menu. The most common methods are:

    • GET: For retrieving data from the API
    • POST: For sending data to the API or triggering actions
    • PUT: For updating existing data
    • PATCH: For partial updates to existing data
    • DELETE: For removing data

API Endpoint URL​

  1. Enter the URL of the FullContact API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters. FullContact API endpoints typically follow the pattern https://api.fullcontact.com/v3/{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 Key authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. For detailed information about FullContact API endpoints and available APIs, see the FullContact API documentation.