Send customer data to more destinations so agents can read at scale

Depending on the workflow, synced SaaS data may need to be sent to different destinations based on the infrastructure required to process it. Ampersand now delivers it directly to:

• Snowflake, BigQuery, Amazon Redshift and ClickHouse for analysis
• Amazon SQS, Google Cloud Pub/Sub, RabbitMQ and Azure Service Bus for processing
• Slack for alerts

Data from each object in an integration can be partitioned to go to its own destination.

Skip the middleware

Previously, getting data into ClickHouse for attribution may have needed an additional tool. Now data can be sent there directly, without custom data pipelines.

Give agents data they can query

An agent that answers by calling a customer’s CRM ends up exhausting the customer’s API limits. With warehouse destinations, agents can read and query data sent directly to a warehouse such as Snowflake.

Receive larger amounts of data in real time with queue destinations

The new queue destinations, Amazon SQS, Google Cloud Pub/Sub, RabbitMQ and Azure Service Bus, allow builders to stream data into their own cloud. With larger data streams, such as backfills, data is queued up so it can be processed more reliably.

Automate alerts to Slack when data delivery fails

Ampersand notifications, such as a connection erroring or a subscription failing to set up, can go to a Slack channel. Notifications can also alert when delivery to a destination fails.

Destinations are set per object, an integration can now map data to destination by purpose:

specVersion: 1.0.0
integrations:
  - name: salesforceSync
    displayName: Salesforce sync
    provider: salesforce
    read:
      objects:
        - objectName: opportunity
          destination: revenueWarehouse   # Snowflake
        - objectName: contact
          destination: enrichmentQueue    # Amazon SQS