Nango

@nango list all active connections and show me which APIs they're connected to

Here are your active Nango connections: 1. **salesforce-prod** (Salesforce) - Connected 3 days ago, last synced 2 hours ago 2. **hubspot-marketing** (HubSpot) - Connected 12 days ago, last synced 45 minutes ago 3. **github-repos** (GitHub) - Connected 8 days ago, last synced 1 hour ago All connections are healthy with no authentication errors. The Salesforce and HubSpot connections have active syncs running on schedule.

This read-only query shows connection metadata without exposing credentials. Useful for auditing which third-party APIs your team has integrated. Requires a valid Nango API key with read permissions. The actual connection list depends on what your team has configured in Nango.

@nango trigger the contact sync action for our hubspot-marketing connection to pull latest contacts

Sync triggered successfully for **hubspot-marketing** connection. **Action:** contact-sync **Provider:** HubSpot **Status:** Running **Sync ID:** sync_8x9k2m4p The sync will fetch contacts updated in the last 24 hours and make them available via your Nango unified API. Estimated completion: 2-3 minutes depending on contact volume.

This demonstrates Nango's core workflow execution capability. The action name ('contact-sync') must match a script defined in your Nango configuration. This is a write operation that initiates data movement from HubSpot into Nango's cache. Check your Nango rate limits if syncing large datasets frequently.

@nango get the available providers and tell me which ones support OAuth 2.0 authentication

Nango supports 150+ providers. Here are OAuth 2.0-enabled providers relevant to common workflows: **CRM:** Salesforce, HubSpot, Pipedrive, Zoho CRM **Project Management:** Asana, Linear, Monday.com, Jira **Communication:** Slack, Microsoft Teams, Discord **Accounting:** QuickBooks, Xero, FreshBooks **Storage:** Google Drive, Dropbox, Box All listed providers use OAuth 2.0 for secure authorization. Each requires registering your app with the provider to obtain client credentials before creating a Nango connection.

This synthesis example combines Nango's provider catalog with the AI's filtering logic. The actual provider list is comprehensive but static — Nango adds new integrations periodically. Useful for scoping integration projects before writing code. The OAuth 2.0 requirement means you'll need to handle redirect flows in your application.

When Nango wins for customer-context aggregation at 10-person scale

A 10-person support team pulls customer data from Salesforce, Stripe, and Zendesk into a shared Switchy workspace every morning. Nango's the right call here because you're orchestrating three OAuth providers with different refresh cycles, and the Trigger Sync tool lets you fire manual updates when a high-value ticket lands. The List Connections tool surfaces which integrations are stale without exposing API keys to the whole team. The threshold: if you're only syncing one provider or your data updates less than twice a week, Nango's overhead (managing provider configs, action triggers) outweighs a simpler direct-API setup. But for multi-source customer context that changes daily, Nango keeps your team from writing refresh logic for each SaaS vendor. Set it up once, trigger syncs from Switchy when context matters.

When Nango handles cross-platform automation for deal stages

A 6-person sales ops team moves deals through HubSpot, Slack notifications, and contract generation in DocuSign. Nango's Trigger Action tool fires workflows when a deal hits "Closed Won"—updating Slack, kicking off DocuSign templates, logging revenue in a spreadsheet. This scenario works because you're chaining actions across providers that each need OAuth, and Nango's scripts configuration centralizes the logic instead of scattering it across Zapier and custom code. The trade-off: if your workflows are simple two-step automations ("HubSpot to Slack"), you don't need Nango's action orchestration—a webhook does it. But when you're triggering 3+ steps across providers with conditional logic, Nango keeps the chain auditable and the credentials secure. Wire it into Switchy so the ops lead can see which workflows ran overnight without touching the Nango dashboard.

When Nango speeds up new-hire integration discovery

A 4-person dev team onboards a junior engineer who needs to understand which third-party APIs the product already connects to. The List Providers and Get Provider Details tools let them query Nango from Switchy and see every configured integration (Stripe, Twilio, Google Calendar) with auth scopes and rate limits in one place. This beats hunting through .env files or Notion docs. The boundary: if your product only integrates 2-3 APIs and they're all documented in your README, Nango's overkill. But once you're managing 5+ OAuth providers with rotating credentials and different refresh behaviors, Nango becomes the source of truth. The junior dev asks Switchy "what Salesforce scopes do we use" and gets the answer in 10 seconds instead of pinging three teammates. Set up read-only access so they can explore without breaking connections.