Creating a Destination
This guide walks you through connecting a new destination to Zeotap.
Step 1: Navigate to Destinations
- Open the Zeotap UI
- Click Destinations in the left sidebar
- Click Add Destination
Step 2: Select a Destination Type
Browse or search the destination catalog. Destinations are organized by category: CRM, Advertising, Marketing, Analytics, Warehouses, Cloud Storage, Streaming, and Other.
Each card shows a short description of the destination; hover over it (or focus it with the keyboard) to read the full text. Click on the destination type you want to connect. Its full description is repeated at the top of the configuration step.
Step 3: Authenticate
The authentication step varies by destination type. Zeotap supports several authentication methods:
OAuth 2.0
For destinations like Salesforce, HubSpot, Google Ads, and Facebook Ads:
- Click Connect with OAuth
- A browser window opens to the destination’s authorization page
- Sign in and grant the requested permissions
- You are redirected back to Zeotap with the connection established
Zeotap automatically manages OAuth token refresh, so you do not need to re-authenticate unless you revoke access.
API Key / Token
For destinations like Braze, Klaviyo, SendGrid, and Pipedrive:
- Navigate to the destination platform’s settings to generate an API key
- Copy the API key
- Paste it into the API Key field in Zeotap
- Click Test Connection to verify
Username & Password
For database destinations like Snowflake, PostgreSQL, MySQL, and Redshift:
- Enter the database Host, Port, and Database name
- Enter the Username and Password
- Configure SSL/TLS settings as needed
- Click Test Connection to verify
Service Account
For GCP-based destinations like BigQuery, Google Cloud Storage, and Google Pub/Sub:
- Create a service account in your GCP project
- Download the JSON key file
- Upload or paste the JSON key into Zeotap
- Click Test Connection to verify
Step 4: Configure Settings
After authentication, configure the destination-specific settings. These vary by destination type but commonly include:
- Instance URL / Subdomain — The URL of your destination instance (e.g.,
myorg.my.salesforce.com) - API Version — Which API version to use for requests
- Data Center / Region — The geographic region of your account
- Bucket / Container — For cloud storage destinations, the target storage location
All required fields are marked with an asterisk (*). Optional fields have sensible defaults.
Step 5: Test the Connection
Click Test Connection to run Zeotap’s multi-step connection test. The test validates:
- Configuration — All required fields are present and correctly formatted
- Authentication — Credentials are valid and not expired
- API Access — The destination API is reachable and responds correctly
- Permissions — The authenticated user/key has the necessary permissions
Each step shows a pass/fail status. If a step fails, Zeotap displays the error message and, where possible, a suggested fix.
Step 6: Save
Click Save to create the destination. You can now use it when creating syncs.
What Happens Next
After creating a destination, the typical next steps are:
- Create a sync — Go to Syncs > Create Sync, select your model as the source and your new destination as the target
- Map fields — Map model columns to destination fields (see Field Mapping)
- Choose a sync mode — Select how data should be written (see Sync Modes)
- Set a schedule — Define how often the sync should run
- Run — Execute the first sync and monitor the results
Managing Destinations
Editing a Destination
- Go to Destinations and click on the destination you want to edit
- Update the configuration or credentials
- Click Test Connection to verify changes
- Click Save
Deleting a Destination
- Go to Destinations and click on the destination
- Click Delete in the settings panel
- Confirm the deletion
Deleting a destination also removes all syncs that use it. This action cannot be undone.
Re-authenticating
If an OAuth token expires or you need to rotate API keys:
- Go to Destinations and click on the destination
- Click Reconnect (for OAuth) or update the API key field
- Click Test Connection and then Save