Which provider name should I use?
2 min
The wizard recognises common vendor names (Outlook, Gmail, Slack) and canonicalises them to OAuth slugs.
The PROVIDER_VOCAB regex maps vendor mentions to OAuth slugs:
Email: "Outlook" → microsoft, "Gmail" → google, "SMTP" → smtp, "Resend" → resend, "SendGrid" → sendgrid, "Mailgun" → mailgun. Calendar: same Microsoft / Google. Messaging: "Slack", "Discord", "Telegram", "Teams" (→ microsoft), "LinkedIn". Code repos: "GitHub", "GitLab". Task management: "Linear", "Asana", "ClickUp", "Monday", "Jira" (→ atlassian), "Notion". CRM: "HubSpot". Commerce: "Stripe", "Shopify", "BigCommerce". Market data: "Polygon", "Finnhub", "Alpha Vantage", "Tiingo", "CoinGecko". Trading: "Alpaca", "Binance", "Kraken". Voice/media: "ElevenLabs", "HeyGen", "Replicate". Web search: "Tavily", "Exa", "Brave Search", "Perplexity".
Use the vendor name (Outlook), not the slug (microsoft) — it reads more naturally and the wizard normalises automatically. If your vendor isn't on this list, the wizard falls back to a generic builtin (e.g. http.request) and asks you to bind a connector by hand.
Live recipes need the desktop
This article is a static preview. The in-app Help sidecar inside Avery NXR can fire each step against your live project — install the desktop to use it interactively.