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 Azure supports pushing files to Azure storage. The Alchemer Azure integration allows Alchemer to send files generated in workflows (such as PDFs or exports) from a link directly to Azure without manual intervention.
Common uses for the Alchemer Azure integration
- Store workflow-generated files (PDFs, CSVs, images) in Azure Blob Storage
- Automate file delivery to Azure for downstream processing
- Centralize file storage for reporting and analytics
- Reduce manual uploads and file handling
- Maintain secure and scalable file storage in Azure
- Trigger external processes based on newly uploaded files
What can the Alchemer Azure integration do?
You will need
- Microsoft Azure Storage Account and Container with appropriate access permissions
- Azure Shared Access Signature (SAS token). More details in the authentication how-to guide.
- An Alchemer plan that includes integrations and the Integration Manager permission enabled.
- Contact us if you are unsure if your plan includes integrations.
Setup Alchemer Azure integration in workflow
Microsoft Azure | Push file to Azure
You will need:
- Azure Blob Storage authentication (SAS token or account key). More details in the authentication how-to guide.
- The Azure container name where files will be created
Configure the action
- Open your workflow in Workflow builder.
- On the right side, drag and drop the Azure connection where you want the action to trigger.
- In the connection box, click the pencil icon in the top right corner.
- Select Azure | Push file to Azure.
- Azure | Authentication: Select an existing authentication or create a new authentication using your SAS URL.
- Azure | Select URL: Select the field in this workflow that contains the URL you would like to push to Azure. This URL must be publicly accessible.
- Azure | File name: You can set a file name, this is optional. The current UNIX timestamp will be used if no file name is set.
- Save the action.
Status codes
- 200: Successfully pushed file to Azure Blob container
- 400: The external integration returned an error.
Testing and Troubleshooting
Testing and Validation
How to test
- Trigger the workflow and monitor individual runs in monitor tab in your workflow
- Click on individual workflow runs to see metadata outputs
- Confirm the file appears in your Azure storage container.
- Use metadata for verification and debugging.
How to verify results
- Check the Azure Blob Storage container for the uploaded file.
- Ensure file name, size, and contents match expectations.
Monitoring Integration Activity
Where to find logs
- Go to Results → Monitor
- Select a the integration step you want to inspect.
What logs display
- Input/Output
Troubleshooting
Authentication issues
- Invalid or expired SAS token
- Incorrect storage account credentials
Upload failures
- Invalid container or file path
- File size or formatting issues
API errors
- Signature mismatch or authorization errors
- Incorrect headers or content type
FAQs
What permissions do I need?
Integration Manager in Alchemer and appropriate Azure storage permissions.
Integration Manager in Alchemer and appropriate Azure storage permissions.
When does the integration run?
When the workflow triggers and reaches the Azure step.
When the workflow triggers and reaches the Azure step.
Can I use multiple Azure actions in one workflow?
Yes. Actions can work independently or together.
Yes. Actions can work independently or together.
Why isn’t my file uploading?
Check authentication, file selection, and destination path configuration.
Check authentication, file selection, and destination path configuration.
What if I need additional functionality?
Contact Alchemer Support for enhancement requests.
Contact Alchemer Support for enhancement requests.
