Skip to main content

Kapost 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 Kapost location.
kapost.png

Kapost

Create a Kapost Destination​

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

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

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

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

    Create content

    • This endpoint automatically creates content in your Kapost account using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
    • The endpoint uses POST requests to https://{subdomain}.kapost.com/api/v1/content where {subdomain} is your Kapost subdomain. The endpoint URL is automatically constructed based on your credential configuration.
    • 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 content data to create.
    • Batch mode is disabled by default for this endpoint, which means each record from your Nexset will be sent as a separate API request. This ensures that each content item is created individually.
    • This endpoint does not automatically create a data source to track the responses received from the Kapost API after each call.

    The request body must be properly formatted JSON that matches the Kapost API specification for creating content. The endpoint requires Basic Authentication with your API token, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. The API token is used as the username in Basic Authentication, with the password set to "x". The subdomain is automatically retrieved from your credential configuration. The request body must contain the required fields for content creation, such as title, content type, and other content information. For detailed information about creating content, including required fields, field names, and request formats, see the Kapost API documentation.

    Create task

    Create task

    • Enter the Content ID in the Content ID field. This is the unique identifier for a specific content item in Kapost to which you want to add a task. You can obtain Content IDs from the "List Content" endpoint or from your Kapost account dashboard.
    • The endpoint uses POST requests to https://{subdomain}.kapost.com/api/v1/content/{content_id}/tasks where {subdomain} is your Kapost subdomain and {content_id} is the Content ID you configured. The endpoint URL is automatically constructed based on your credential configuration and the Content ID you specify.
    • 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 task data to create.
    • Batch mode is disabled by default for this endpoint, which means each record from your Nexset will be sent as a separate API request. This ensures that each task is created individually.
    • This endpoint does not automatically create a data source to track the responses received from the Kapost API after each call.

    The request body must be properly formatted JSON that matches the Kapost API specification for creating tasks. The endpoint requires Basic Authentication with your API token, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. The API token is used as the username in Basic Authentication, with the password set to "x". The subdomain is automatically retrieved from your credential configuration. The Content ID identifies which content item to add the task to. The request body must contain the required fields for task creation, such as task name, assignee, and other task information. For detailed information about creating tasks, including required fields, field names, and request formats, see the Kapost API documentation.

Configure Manually​

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

API Endpoint URL​

  1. Enter the URL of the Kapost 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://), your Kapost subdomain, and any required path parameters. Kapost API endpoints typically follow the pattern https://{subdomain}.kapost.com/api/v1/{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 Basic Authentication with your API token, which is handled automatically by your credential configuration. The API token is used as the username in Basic Authentication, with the password set to "x". The subdomain is automatically retrieved from your credential configuration. For detailed information about Kapost API endpoints, authentication, and available APIs, see the Kapost API documentation.