Skip to main content

Seismic Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Seismic location.
seismic_api.png

Seismic

Create a Seismic Destination​

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

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

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

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

    Creates a new post in a Seismic channel. Use this endpoint to publish content announcements, sales alerts, or data-driven updates as Seismic channel posts directly from a Nexla data flow. The post content is sent as a JSON payload to the Seismic Posts API at https://api.seismic.com/posts.

    • No additional endpoint parameters are required for this template. The post content is derived from the mapped Nexset fields, which are sent as a JSON body to the Seismic Posts API.
    • Ensure that the Nexset being sent to this destination includes the fields required by the Seismic Posts API. Refer to the Seismic Developer Portal for the required request body schema for creating a post.
    • The OAuth2 credential used for this destination must include the appropriate scope for writing posts (e.g., seismic.channels.manage).

    Each record in the Nexset will be sent to the Seismic Posts API as a separate API call (unless record batching is enabled). For high-volume scenarios, consider configuring record batching in the manual configuration settings.

    Update Post

    Updates an existing post in Seismic. Use this endpoint when you need to modify the content of previously published Seismic posts. The update is sent as a JSON PUT request to https://api.seismic.com/posts/{post_id}.

    • Post ID (Required): Enter the unique identifier of the post to update in the Post ID field. This value is required. The Post ID must correspond to an existing post in your Seismic tenant. Post IDs can be obtained from the Seismic connector's List Posts or Get Post data source endpoints.
    • Ensure that the Nexset being sent to this destination includes all fields required by the Seismic update post request body. Only the fields included in the payload will be updated — existing fields not included in the payload will retain their current values.
    • The OAuth2 credential used for this destination must include the appropriate scope for updating posts (e.g., seismic.channels.manage).

    To update multiple posts in a single flow, ensure that each record in the Nexset includes the correct Post ID for the post to be updated. Each record is sent as a separate PUT request to the Seismic API.

Configure Manually​

Seismic destinations can be manually configured to send data to any valid Seismic API endpoint. Use manual configuration to access Seismic write endpoints beyond the pre-built templates, such as endpoints in the Seismic Content Management API, Integration API, or other Seismic API surfaces.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Seismic API after each call to a new Nexla webhook data source.

API Method​

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

  2. Select the API method that will be used for calls to the Seismic API from the Method pulldown menu. Common methods for Seismic write operations are:

    • POST: For creating new records in Seismic (e.g., creating posts, triggering workflows)
    • PUT: For replacing an existing record entirely (e.g., updating a post)
    • PATCH: For partial updates to an existing record

Data Format​

  1. Select the format in which the Nexset data will be sent to the Seismic API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The Seismic API expects data in JSON format for all write operations.

API Endpoint URL​

  1. Enter the URL of the Seismic API endpoint to which you want to send the Nexset data in the URL field. All Seismic API base URLs begin with https://api.seismic.com/. For update or upsert operations, include the ID of the object to be updated at the end of the URL (e.g., https://api.seismic.com/posts/{post_id}).

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include an Authorization header — it is automatically handled by the Seismic OAuth2 credential. The Content-Type: application/json header is also set automatically based on the selected data format.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Seismic destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings.

Response Webhook​

Optional

Nexla can automatically send the response received from the Seismic API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call, such as the created post ID or error details.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Seismic API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Seismic API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Seismic API using the current settings.

Save & Activate the Destination​

  • Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to Seismic, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to Seismic until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.