Skip to main content

Goldcast 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 Goldcast location.
goldcast_api.png

Goldcast

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

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

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

    Goldcast destinations can also be configured manually, allowing you to send data to Goldcast 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 Goldcast endpoints. Each template is designed specifically for the corresponding Goldcast endpoint, making destination setup easy and efficient.

Endpoint Settings​

  • Select the endpoint to which this destination will send 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 destination for this endpoint.

    Create Event

    Creates a new Goldcast event with the specified configuration. Use this endpoint to programmatically provision events from external event management systems, CRM platforms, or automated scheduling workflows.

    • Sends a POST request to the Goldcast events endpoint with the event configuration payload in the request body.
    • Returns the created event object including the newly assigned event ID.

    Requires the events:write security role. Enable the Response Webhook option to capture the new event ID for use in downstream flows such as adding agenda items or inviting members.

    Create Ticket Type

    Creates a new ticket type for a Goldcast event. Use this endpoint to programmatically define registration tiers, access levels, or pricing options for events managed through Nexla.

    Enable the Response Webhook option to capture the new ticket type ID for use in registration and attendee management flows.

Configure Manually​

Goldcast destinations can also be manually configured to send data to any valid Goldcast API endpoint. A common use case is creating event registrants programmatically — for example, syncing registrant records from a CRM, marketing automation platform, or a custom registration form into a Goldcast event.

You can also configure Nexla to automatically send the response received from the Goldcast API after each call to a new Nexla webhook data source.

First, select the API method that will be used for calls to the Goldcast API from the Method pulldown menu. Common methods for writing data to Goldcast include:

  • POST: For creating new records, such as event registrants
  • PUT: For replacing an existing record in full
  • PATCH: For partially updating an existing record

Data Format​

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

    Goldcast's registrant creation endpoint (https://backend.goldcast.io/core/user/registration/) expects data as application/x-www-form-urlencoded. Select the appropriate content format to match the Goldcast API endpoint's requirements.

API Endpoint URL​

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

    For creating event registrants, use the Goldcast registration endpoint: https://backend.goldcast.io/core/user/registration/

    This endpoint requires the following fields in the request body:

    • event_id: The unique identifier of the target Goldcast event.
    • form_id: The unique identifier of the Goldcast registration form associated with the event.
    • email: The registrant's email address.
    • Additional registrant fields as defined in the event's registration form (e.g., first name, last name, company).

To find your event ID and form ID, log in to Goldcast Studio, navigate to the target event, and open the registration form settings. The IDs are displayed in the form configuration view. Additional details are available in the Goldcast registration 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 any headers already present in the credentials. The Goldcast API token configured in your credential is automatically applied to all requests.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Goldcast 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. Some algorithms require additional settings—click on an algorithm listed below to view instructions for configuring these settings.

Response Webhook​

Optional

Nexla can automatically send the response received from the Goldcast 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 — for example, confirming successful registrant creation or capturing error details for failed submissions.

  • 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 Goldcast 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​

After all endpoint settings have been configured, Nexla can send a test payload to the Goldcast 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 Goldcast 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 send the data to the configured Goldcast endpoint, open the destination resource menu, and select Activate.

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