- Getting started
- Notifications
- Licensing
- Troubleshooting
- Connector Builder
- Act! 365
- Active Directory - Preview
- ActiveCampaign
- Adobe Acrobat Sign
- Adobe PDF Services
- Amazon Bedrock
- Amazon Connect
- Amazon Polly
- Amazon SES
- Amazon Transcribe
- Amazon Web Services
- Anthropic Claude
- Asana
- AWeber
- Azure AI Document Intelligence
- Azure AI Foundry
- Azure Maps
- BambooHR
- Box
- Brevo
- Calendly
- Campaign Monitor
- Cisco Webex Teams
- Citrix Hypervisor
- Citrix ShareFile
- Clearbit
- Confluence Cloud
- Constant Contact
- Coupa
- Customer.io
- Databricks Agent
- Datadog
- DeepSeek
- Deputy
- DocuSign
- Drip
- Dropbox
- Dropbox Business (Legacy)
- Egnyte
- Eventbrite
- Exchange Server - Preview
- Exchangerates
- Expensify
- Facebook
- Freshbooks
- Freshdesk
- Freshsales
- Freshservice
- GetResponse
- GitHub
- Gmail
- Google Cloud Platform
- Google Docs
- Google Drive
- Google Forms
- Google Maps
- Google Sheets
- Google Speech-to-Text
- Google Tasks
- Google Text-to-Speech
- Google Vertex
- Google Vision
- Google Workspace
- GoToWebinar
- Greenhouse
- Hootsuite
- HTTP Webhook
- Hubspot CRM
- HubSpot Marketing
- HyperV - Preview
- Icertis
- iContact
- Insightly CRM
- Intercom
- Jina.ai
- Jira
- Keap
- Klaviyo
- LinkedIn
- Mail
- Mailchimp
- MailerLite
- Mailgun
- Mailjet
- Marketo
- Microsoft 365
- Microsoft Azure
- Microsoft Azure Active Directory
- Microsoft Azure OpenAI
- Microsoft Dynamics 365 CRM
- Microsoft OneDrive & Sharepoint
- Microsoft Outlook 365
- Microsoft Power Automate
- Microsoft Sentiment
- Microsoft Teams
- Microsoft Translator
- Microsoft Vision
- Miro
- NetIQ eDirectory
- Okta
- OpenAI
- OpenAI V1 Compliant LLM
- Oracle Eloqua
- Oracle NetSuite
- PagerDuty
- PayPal
- PDFMonkey
- Perplexity
- Pinecone
- Pipedrive
- QuickBooksOnline
- Quip
- Salesforce
- Salesforce Marketing Cloud
- SAP BAPI
- SAP Cloud for Customer
- SAP Concur
- SAP OData
- SendGrid
- ServiceNow
- Shopify
- Slack
- SmartRecruiters
- Smartsheet
- Snowflake
- Snowflake Cortex
- Stripe
- Sugar Enterprise
- Sugar Professional
- Sugar Sell
- Sugar Serve
- System Center - Preview
- TangoCard
- Todoist
- Trello
- Twilio
- UiPath GenAI Activities
- HTTP
- UiPath Orchestrator
- VMware ESXi vSphere
- watsonx.ai
- WhatsApp Business
- WooCommerce
- Workable
- Workday
- Workday REST
- X (formerly Twitter)
- Xero
- YouTube
- Zendesk
- Zoho Campaigns
- Zoho Desk
- Zoho Mail
- Zoom
- ZoomInfo
Working with files
Upload files to a provider from a custom connector built with Connector Builder for Integration Service in Automation Suite, using multipart parameters.
Connectors built with Connector Builder can upload files to a provider. Uploads are configured on the API resource, as a multipart parameter, and surfaced as an activity input field. The HTTP Request activity does not support files, so it is not an alternative.
Uploading a file
A file is uploaded through a parameter on the API resource. To configure one:
- In the Activity designer, open the resource and select the parameter that carries the file.
- Under Parameter settings, set Parameter type to multipart.
- Set Data type to file.
Connector Builder derives the request content type from the parameter: a resource that has a multipart parameter is sent as multipart/form-data, and a resource that does not is sent as application/json. You do not set the content type yourself.
A resource can mix locations. Alongside the file parameter you can keep parameters in the query, path, header, or body, and add further multipart parameters of other data types — for example a string parameter carrying the file name.
The parameter then appears as a file input on the generated activity, and in the Send Request dialog as a Choose file control, so you can test the resource before you publish.
To inspect or modify the parts of a multipart request from a connector script, use the multipart_hook_context_items variable. For details, see Global scripts.
First-party connectors already ship this pattern — the Box connector uses a file-typed multipart parameter for its upload resources.
Known limitations
- Field generation: Connector Builder does not generate fields for a resource that has a multipart parameter, and says so in the Send Request dialog, under Generate resource fields. Define the fields for such a resource manually.
- Request body editor: The request body editor accepts JSON. Multipart requests are expressed through parameters on the API resource.