Skip to main content

LinkedIn Citadel 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 LinkedIn Citadel location.
licit_api.png

LinkedIn Citadel

Create a LinkedIn Citadel Destination​

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

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

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

    LinkedIn Citadel destinations can also be configured manually, allowing you to send data to LinkedIn Citadel 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 LinkedIn Citadel endpoints. Each template is designed specifically for the corresponding LinkedIn Citadel 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 Sales Lead

    Create Sales Lead

    • This endpoint automatically creates a sales lead from each record of your Nexset in your LinkedIn Citadel account. No additional configuration is required beyond selecting this endpoint template. Check the API documentation link for the required record schema and field names.
    • The endpoint uses POST requests to https://api.linkedin.com/v2/salesLeads. The endpoint URL is fixed and does not require any path parameters.
    • 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 sales lead data to create. The data mapping is set to automatic mode, which means Nexla will automatically map fields from your Nexset to the LinkedIn Citadel API schema.
    • This endpoint does not automatically create a data source to track the responses received from the LinkedIn Citadel API after each call.

    The request body must be properly formatted JSON that matches the LinkedIn Citadel API specification for creating sales leads. The endpoint requires OAuth2 authentication with an access token, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. The access token is sent in the Authorization: Bearer {access_token} header for all API requests. The request body must contain the required fields for sales lead creation according to the LinkedIn Citadel API schema. The data mapping is set to automatic mode, which means Nexla will automatically map fields from your Nexset to the API schema. For detailed information about creating sales leads, including required fields, field names, and request formats, check the API documentation link provided in the endpoint configuration or refer to the LinkedIn Sales Navigator API documentation.

Configure Manually​

LinkedIn Citadel destinations can be manually configured to send data to any valid LinkedIn Citadel 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 LinkedIn Citadel 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 LinkedIn Citadel API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The LinkedIn Citadel API typically uses JSON format for request bodies.

API Endpoint URL​

  1. Enter the URL of the LinkedIn Citadel 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. LinkedIn Citadel API endpoints typically follow the pattern https://api.linkedin.com/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 OAuth2 authentication with an access token, which is handled automatically by your credential configuration. The access token is sent in the Authorization: Bearer {access_token} header for all API requests. For detailed information about LinkedIn Citadel API endpoints, authentication, and available APIs, see the LinkedIn Sales Navigator API documentation.