Skip to main content

Coda 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 Coda location.
coda_api.png

Coda

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 Coda location.

Create a Coda Destination​

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

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

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

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

    This endpoint creates a new Coda document. Use this endpoint when you need to programmatically create documents, initialize document structures, or automate document creation workflows.

    • This endpoint sends data to Coda's document creation API. The request body should contain the document configuration in JSON format following Coda's document creation structure.
    • Each record in your Nexset will create a new document, and the response will include the document ID and metadata for each created document.
    • The endpoint automatically creates a corresponding data source for each created document, allowing you to track document creation.

    The request body should follow Coda's document creation format, including document name, description, and optional settings. For complete information about creating documents, see the Coda Create Doc API Documentation.

    Create Page

    This endpoint creates a new page within a specific Coda document. Use this endpoint when you need to programmatically add pages to documents, organize content, or automate page creation workflows.

    • Enter the Document ID in the Document ID field. This should match the exact ID of a document in your Coda account where the page will be created.
    • This endpoint sends data to Coda's page creation API. The request body should contain the page configuration in JSON format following Coda's page creation structure.
    • Each record in your Nexset will create a new page, and the response will include the page ID and metadata for each created page.
    • The endpoint automatically creates a corresponding data source for each created page, allowing you to track page creation.

    The request body should follow Coda's page creation format, including page name and optional settings. Document IDs can be found using the "List Documents" source endpoint. For complete information about creating pages, see the Coda Insert Page API Documentation.

    Insert/Update Rows

    This endpoint inserts or updates rows in a specific table within a Coda document. Use this endpoint when you need to add new data to tables, update existing rows, or sync data from other systems to Coda tables.

    • Enter the Document ID in the Document ID field. This should match the exact ID of a document in your Coda account.
    • Enter the Table ID in the Table ID field. You can find this ID by using the "List Tables" source endpoint to retrieve available tables and their corresponding IDs.
    • Optionally, check the Disable Parsing checkbox to disable automatic parsing of values. When unchecked, Coda will automatically parse values based on column types.
    • This endpoint sends data to Coda's upsert rows API. The request body should contain the row data in JSON format following Coda's row format structure.
    • Each record in your Nexset will be inserted or updated in the table. If a row with a matching key exists, it will be updated; otherwise, a new row will be inserted.
    • The endpoint supports batch mode, allowing multiple rows to be processed efficiently in a single API call.
    • The endpoint automatically creates a corresponding data source for each upsert operation, allowing you to track row changes.

    The upsert operation uses row keys to determine whether to insert or update. If a row with the same key exists, it will be updated; otherwise, a new row will be inserted. The request body should follow Coda's row format, with column IDs or names mapping to values. For complete information about upserting rows, see the Coda Upsert Rows API Documentation.

    Update Row

    This endpoint updates a specific row in a table within a Coda document. Use this endpoint when you need to update existing row data, modify specific fields, or sync updates from other systems to Coda tables.

    • Enter the Document ID in the Document ID field. This should match the exact ID of a document in your Coda account.
    • Enter the Table ID in the Table ID field. You can find this ID by using the "List Tables" source endpoint to retrieve available tables and their corresponding IDs.
    • Enter the Row ID in the Row ID field. You can find row IDs by using the "List Rows" source endpoint to retrieve available rows and their corresponding IDs.
    • Optionally, check the Disable Parsing checkbox to disable automatic parsing of values. When unchecked, Coda will automatically parse values based on column types.
    • This endpoint sends data to Coda's update row API. The request body should contain the updated row data in JSON format following Coda's row format structure.
    • Each record in your Nexset will update the specified row with the provided data.

    Row IDs are unique identifiers within a table. You can find row IDs by using the "List Rows" source endpoint first. The request body should follow Coda's row format, with column IDs or names mapping to updated values. For complete information about updating rows, see the Coda Update Row API Documentation.

    Delete Rows

    This endpoint deletes rows from a specific table within a Coda document. Use this endpoint when you need to remove data from tables, clean up outdated rows, or sync deletions from other systems to Coda tables.

    • Enter the Document ID in the Document ID field. This should match the exact ID of a document in your Coda account.
    • Enter the Table ID in the Table ID field. You can find this ID by using the "List Tables" source endpoint to retrieve available tables and their corresponding IDs.
    • This endpoint sends data to Coda's delete rows API. The request body should contain the row IDs to delete in JSON format following Coda's delete rows structure.
    • Each record in your Nexset will specify rows to delete, and the endpoint will remove the specified rows from the table.

    The request body should follow Coda's delete rows format, specifying which rows to delete by their IDs. For complete information about deleting rows, see the Coda Delete Rows API Documentation.

    Push Button

    This endpoint triggers a button control on a specific row in a Coda table. Use this endpoint when you need to programmatically trigger button actions, automate workflows, or execute button-based automations.

    • Enter the Document ID in the Document ID field. This should match the exact ID of a document in your Coda account.
    • Enter the Table ID in the Table ID field. You can find this ID by using the "List Tables" source endpoint to retrieve available tables and their corresponding IDs.
    • Enter the Row ID in the Row ID field. You can find row IDs by using the "List Rows" source endpoint to retrieve available rows and their corresponding IDs.
    • Enter the Column ID in the Column ID field. This should be the ID of the button column that will be triggered. You can find column IDs by using the "List Columns" source endpoint.
    • This endpoint sends a POST request to trigger the button, and the button's associated action will be executed.

    Button controls in Coda can trigger automations, formulas, or other actions. Column IDs for button columns can be found using the "List Columns" source endpoint. For complete information about pushing buttons, see the Coda Push Button API Documentation.

    Trigger Automation

    This endpoint triggers a webhook-invoked automation within a Coda document. Use this endpoint when you need to programmatically trigger Coda automations, execute automation workflows, or integrate external systems with Coda automations.

    • Enter the Document ID in the Document ID field. This should match the exact ID of a document in your Coda account.
    • Enter the Automation Rule ID in the Automation Rule ID field. This should be the ID of the automation rule that will be triggered. You can find automation rule IDs in the Coda document's automation settings.
    • This endpoint sends data to Coda's automation trigger API. The request body should contain any data needed by the automation in JSON format.
    • Each record in your Nexset will trigger the specified automation with the provided data.

    Automation rules in Coda can be configured to respond to webhook triggers. The automation rule ID can be found in the document's automation settings. For complete information about triggering automations, see the Coda Trigger Webhook Automation API Documentation.

Configure Manually​

Coda destinations can be manually configured to send data to any valid Coda API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Coda 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 Coda API from the Method pulldown menu. The most common methods for Coda destinations are:

    • POST: For creating documents, pages, rows, or triggering actions (most common)
    • PUT: For updating existing rows or resources
    • DELETE: For removing rows or resources

Data Format​

  1. Select the format in which the Nexset data will be sent to the Coda API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call.

The Coda API accepts JSON in request bodies and returns JSON in response bodies. Ensure you select JSON as the content format for Coda API destinations. For complete information about Coda API request formats, see the Coda API Documentation.

API Endpoint URL​

  1. Enter the URL of the Coda API endpoint to which you want to send the Nexset data in the URL field. For update/delete operations, include the ID of the object to be updated or deleted at the end of the URL.

Coda API URLs typically follow the format: https://coda.io/apis/v1/docs/{docId}/tables/{tableId}/rows for row operations, or https://coda.io/apis/v1/docs for document operations. Replace {docId} and {tableId} with actual document and table identifiers. For complete information about Coda API endpoints, see the Coda API Documentation.

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 authentication headers (Authorization: Bearer {token}) as these are automatically included from your credentials. However, you may need to include additional headers for specific Coda API features. The Content-Type header should be set to application/json for Coda API requests.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Coda 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.

Record batching is particularly useful for Coda's upsert rows endpoint, which supports batch operations. Batching can improve performance when sending large volumes of data to Coda tables. For complete information about Coda API batching capabilities, see the Coda API Documentation.