- Getting started
- Notifications
- Licensing
- Troubleshooting
- Coding agents
- Connector Builder
- Act! 365
- ActiveCampaign
- Active Directory - Preview
- Adobe Acrobat Sign
- Adobe PDF Services
- Agent 2 Agent - Preview
- Amazon Bedrock
- Amazon Connect
- Amazon Polly
- Amazon SES
- Amazon Transcribe
- Amazon Web Services
- Anthropic Claude
- Asana
- AWeber
- Azure AI Document Intelligence
- Azure Defender for Cloud
- Azure Maps
- BambooHR
- Box
- Brevo
- Calendly
- Campaign Monitor
- Cisco Webex Teams
- Citrix Hypervisor
- Citrix ShareFile
- Clearbit
- Confluence Cloud
- Constant Contact
- Coupa
- CrewAI – Preview
- Customer.io
- Database Hub
- Databricks - Preview
- Databricks Agent
- Datadog
- DeepSeek
- Deputy
- Discord - Preview
- DocuSign
- Drip
- Dropbox
- Dropbox Business
- Egnyte
- Epic FHIR - Preview
- Eventbrite
- Exchangerates
- Exchange Server - Preview
- Expensify
- Facebook
- Freshbooks
- Freshdesk
- Freshsales
- Freshservice
- GetResponse
- GitHub
- Gmail
- Google Cloud Platform
- Google Docs
- Google Drive
- Google Forms - Preview
- Google Maps
- Google Sheets
- Google Speech-to-Text
- Google Text-to-Speech
- Google Tasks - Preview
- Google Vertex
- Google Vision
- Google Workspace
- GoToWebinar
- Greenhouse
- Hootsuite
- HTTP
- HTTP Webhook
- Hubspot CRM
- HubSpot Marketing
- HyperV - Preview
- Icertis
- iContact
- Insightly CRM
- Intercom
- Jina.ai
- Jira
- Keap
- Klaviyo
- LinkedIn
- Mail
- Mailchimp
- Mailgun
- Mailjet
- MailerLite
- Marketo
- MCP
- Microsoft 365
- Microsoft Azure
- Microsoft Azure Active Directory
- Microsoft Azure AI Foundry
- Microsoft Azure OpenAI
- Microsoft Azure Sentinel
- Microsoft Dynamics 365 CRM
- Microsoft OneDrive & Sharepoint
- Microsoft Outlook 365
- Microsoft Power Automate
- Microsoft Sentiment
- Microsoft Sentinel Threat Intelligence
- Microsoft Teams
- Microsoft Translator
- Microsoft Vision
- Miro
- NetIQ eDirectory
- Nvidia NIM
- Okta
- OpenAI
- OpenAI V1 Compliant LLM
- Oracle Eloqua
- Oracle NetSuite
- PagerDuty
- PayPal
- PDFMonkey
- Perplexity
- Pinecone
- Pipedrive
- QuickBooksOnline
- Quip
- Salesforce
- Salesforce Agentforce & Flows
- 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
- TypeSafe - Preview
- UiPath Apps - Preview
- UiPath Data Fabric
- UiPath Test Manager
- UiPath GenAI Activities
- UiPath Orchestrator
- X (formerly Twitter)
- Xero
- watsonx.ai
- WhatsApp Business
- WooCommerce
- Workable
- Workday
- Workday REST
- VMware ESXi vSphere
- YouTube
- Zendesk
- Zoho Campaigns
- Zoho Desk
- Zoho Mail
- Zoom
- ZoomInfo
Chaining requests with Next resource
Run a second Connector Builder resource automatically after the first one completes, using the first response, to build activities that need more than one API call.
Some provider APIs don't return what you need in a single request. To download an attachment, for example, you might first request the record that holds the file ID, and then request the file itself.
Next resource handles these cases. When a resource has a next resource, Connector Builder sends the next resource's request automatically after the first request completes, and passes the first response to it.
How a chain runs
- The resource sends its request and receives the response.
- The next resource sends its request. Its scripts can read the response body and headers of the previous request.
- If the next resource also has a next resource, the chain continues.
- The activity returns the response of the last request in the chain.
The activity's output fields are based on the response of the last resource in the chain.
Each request in the chain reuses the path variables, headers, and query parameters of the original request.
Setting a next resource
- In Connector Builder, open your custom connector and select the resource that sends the first request.
- Select the Advanced tab.
- In Next resource, search for the resource to run next by its method or path, and then select it. A resource can't be its own next resource.
- Save your changes.
The resource you select as the next resource is still listed as its own activity, unless you hide it.
To use the previous response, add a pre-request script to the next resource on its Scripts tab. For details on scripts, see Scripts.
Using the previous response
The pre-request script of the next resource can read the following variables:
| Variable | Access | Description |
|---|---|---|
request_previous_response | Read | Response body of the previous request in the chain. null if the resource doesn't run as part of a chain. |
request_previous_response_headers | Read | Response headers of the previous request in the chain. null if the resource doesn't run as part of a chain. |
request_previous_vendor_path | Read | The path of the previous request in the chain. null if the request isn't part of a chain. |
For example, the first resource gets a record that holds a file ID, and the next resource downloads the file. The pre-request script of the next resource reads the file ID from the previous response and adds it to the request path:
var previous = request_previous_response || {};
done({ request_vendor_path: '/files/' + previous.file_id + '/content' });
var previous = request_previous_response || {};
done({ request_vendor_path: '/files/' + previous.file_id + '/content' });
The path and the file_id property depend on your provider's API.
Limits
- A chain can include up to five requests, counting the first one. A longer chain fails with the error
Resources chaining cannot exceed more than 5 calls. - A chain stops after a request that streams its response. The resources set after it don't run.