Azure Blob Storage destinations - Ampersand

For more information on destinations, see the Destinations page. When new data is read from a SaaS instance via a Read Action or Subscribe Action, Ampersand writes the payload as objects to your Azure Blob Storage container.

Prerequisites

Before setting up an Azure Blob Storage destination, ensure that you have:

An Azure Storage account
A blob container to write to
The storage account’s access key

Data format

Ampersand writes each read or subscribe message as a JSON object to your container. The full payload schema is defined in webhook.yaml.

Create an Azure Blob Storage destination

Go to the Destinations page in the Ampersand Dashboard and create a new Azure Blob Storage destination. You’ll need to provide:

Field	Type	Required	Example	Description
Destination name	string	Yes	`ampersandAzureBlob`	Alias to reference in your `amp.yaml` file
Account	string	Yes	`mystorageaccount`	Azure Storage account name
Container	string	Yes	`ampersand-data`	Blob container to write objects to
Access key	string	Yes		Storage account access key

Refer to the destination in your integration

After creating your Azure Blob Storage destination, reference it in your amp.yaml file:

specVersion: 1.0.0
integrations:
  - name: salesforceToAzureBlob
    displayName: Salesforce to Azure Blob Storage
    provider: salesforce
    read:
      objects:
        - objectName: account
          destination: ampersandAzureBlob
        - objectName: contact
          destination: ampersandAzureBlob

⌘I