Overview
Microsoft Azure is a cloud computing platform offering storage, compute, identity, and data services. Organizations use Azure Blob Storage to securely store, manage, and distribute unstructured data at scale.
The Alchemer integration with Microsoft Azure supports automated workflow initiation based on CSV file contents.
The Alchemer → Microsoft Azure Workflow integration allows Alchemer to read a CSV file, extract each row, and trigger a separate workflow execution for every row—fully automating bulk operations, data processing, and downstream integrations without manual intervention.
Common uses for the Alchemer Microsoft Azure integration
- Send one workflow request per CSV row into Azure Logic Apps or Azure Functions
- Automate batch updates into Azure-based systems
- Drive workflow branching or routing using CSV values
- Trigger external API calls through Azure workflows for each data row
- Reduce manual processing of large CSV datasets
What can the Alchemer Microsoft Azure integration do?
You will need
- Azure Shared Access Signature (SAS token). More details in the authentication how-to guide.
- An Alchemer plan that includes integrations with Workflow and the Integration Manager permission enabled.
- Contact us if you are unsure if your plan includes integrations.
Setup Alchemer Microsoft Azure integration in Workflow
Microsoft Azure | Start workflow for each row in a CSV file
You will need:
- Azure Blob Storage authentication (SAS token or account key). More details in the authentication how-to guide.
- A CSV file exists in your Azure Blob Storage container
Configure the action
- Open your workflow in Workflow Builder.
- On the Select Initiator pop up select the Microsoft Azure initiator.
- Select Azure | Start workflow for each row in a CSV file.
- Azure | Authentication: Select an existing authentication or create a new authentication using your SAS URL.
- Azure | Source directory: Enter the directory where your source CSV files are located. You can enter a forward slash / if you would like it to search in the entire container.
- Azure | Selected headers: Please insert a comma separated list of headers that your CSV(s) will contain. This will be used for the output merge codes in the workflow. The headers here must exactly match the headers in the CSV in your container.
- Azure | Schedule for runs: Set the schedule for how frequently you want to get the CSV files from your Azure Blob Storage container.
- Save the action.
Status codes
- 200: Successfully triggered the Azure workflow for each row
- 400: The external integration returned an error
Testing and Troubleshooting
Testing and Validation
How to test
-
Trigger the workflow and monitor individual runs in the Monitor tab.
- Click on each run to view metadata outputs for each row sent to Azure.
How to verify results
- Set a send email action to yourself with action metadata included.
- Verify that each CSV row generated an independent workflow run.
Monitoring Integration Activity
Where to find logs
- Go to Monitor
- Check the individual workflow steps
What logs display
- Inputs sent per row
- Workflow output or returned status
Troubleshooting
Authentication issues
- Incorrect or expired schedule
- Invalid Azure SAS URL
CSV issues
- Incorrect header formatting
- Missing required columns
- Invalid characters or malformed data
API errors
- Azure validation failures
- Logic App or Function runtime errors
FAQs
What permissions do I need?
Integration Manager in Alchemer and the Azure permission.
Integration Manager in Alchemer and the Azure permission.
When does the integration run?
On the set schedule.
On the set schedule.
Why isn’t my workflow triggering?
Check the Monitor tab for CSV issues, authentication errors, or Azure workflow failures.
Check the Monitor tab for CSV issues, authentication errors, or Azure workflow failures.
What if I need additional functionality?
Contact Alchemer Support for enhancement requests.
Contact Alchemer Support for enhancement requests.
