The biggest piece of feedback we've gotten from early users was not about the AI, the templates, or the workflow language. It was this: connecting tools took too long. General Input is amazing at building agents and workflows once it has the credentials it needs. Getting the credentials in was the bottleneck.
Register an OAuth app inside Salesforce. Paste an API token for HubSpot. Submit Microsoft Graph scopes to InfoSec for review. Reconnect Google Workspace because a token expired. A two-minute workflow sitting behind two hours of configuration.
What shipped this week
In the last week, we added one-click integrations for dozens of providers. The full Microsoft Suite -- Outlook, Teams, OneDrive, SharePoint, Excel, Planner, To Do. The full Google Suite -- Gmail, Drive, Calendar, Sheets, Docs, Slides, Tasks, Meet, Analytics, Forms. HubSpot, Salesforce, Reddit, Typeform, Attio, Airtable, Box, Dropbox, Basecamp, Calendly, GitHub, Linear, QuickBooks, Shopify, Stripe integrations, and more.
The flow is now: pick a provider, click connect, authorize in the provider's own consent screen, done. No app registration inside your tenant. No tokens pasted into a form. No InfoSec review to get a basic integration into the hands of a builder.
Cloud friction removed, private deployment values kept
We chose to remove this friction for cloud customers, but stayed true to our values of enabling private deployment of AI by letting users bring their own OAuth in those cases. For regulated industries, enterprises with data residency requirements, or anyone still thinking about last year's Salesloft Drift incident where a single compromised OAuth app exposed data in 700+ Salesforce instances, bring-your-own OAuth is available for every provider where it matters. Register your own app, point General Input at it, and every token your users generate stays with you.
The security model underneath didn't regress. Credentials never reach the AI. They're encrypted at rest, injected into API calls at runtime, and stripped from request and response payloads before the model ever sees them. Every external call is audit-logged with the agent identity, the user on whose behalf it ran, and the exact endpoint and payload. Okta is launching "Okta for AI Agents" on April 30 with a blueprint built around the question "what can your agents connect to." This is our answer.
What you can build in an afternoon now
The point of shipping this was to stop making the connection step the thing that kills the workflow. Here are five workflows a RevOps team can stand up in an afternoon now that the integrations take minutes:
- HubSpot Lead to Salesforce Opportunity Sync with Enrichment -- When a HubSpot contact hits MQL, enrich the company from the email domain, create the matching Salesforce opportunity, and post the handoff to a Microsoft Teams channel. Two CRMs stay in sync without a brittle Zap.
- Stalled Salesforce Opportunity Alert to Microsoft Teams -- Daily scan for opportunities with no activity in 14 days. Enrich the account with recent news, generate an outreach angle with AI, and DM the Account Owner directly in Teams.
- Weekly Pipeline Health Briefing to Outlook -- Every Monday at 7am, combine Salesforce pipeline and HubSpot funnel data into an AI-written briefing with pipeline coverage, stage movement, and at-risk deals. Emailed to leadership via Outlook.
- Reddit Brand Mention to HubSpot Contact -- Monitor Reddit for mentions of your company or product. When a relevant post is found, enrich the author where possible and create a HubSpot contact with the Reddit thread logged as a note.
- New Salesforce Lead Research Brief to OneDrive -- On every new Salesforce lead, run person and company enrichment, generate a structured research brief, save it to the account's OneDrive folder, and ping the Account Owner in Teams with the link.
Each one runs on connected tools, costs pennies per execution, and -- now -- takes minutes of setup instead of an afternoon.
The biggest unlock was removing a step
The useful lesson here isn't product design. It's that the best feedback is often about what you should delete, not add. Our early users didn't want a better integration configuration page. They wanted it to disappear. The floor that AI automation needs to cross isn't model quality. It's the friction between the idea and the first running workflow. Connecting tools was the friction that kept showing up. So we removed it.
If you tried General Input early on and got stuck at setup, come back. The thing that stopped you is gone.