Connecting apps
A connector is an app your workflows can call. Add one from Connectors → Add connector.
Built-in operations vs generic REST
Apps marked built-in ops come with ready-made, tested operations — pick the app, pick the action, fill in guided fields. Apps marked generic REST are a starting point: the base URL and authentication are set up, and you supply endpoint paths from that app's API documentation.
Any API, via OpenAPI
If the app publishes an OpenAPI specification, import it by URL or by pasting it and you get properly typed operations with real field names. Discover searches a public directory of specifications, so you often don't have to find the file yourself.
Credentials
Connectors support no auth, bearer tokens, API keys, basic auth, and OAuth 2. All credentials are encrypted, write-only in the interface (you can replace one but never read it back), and stripped from run traces. You can hold several named connections for the same app — production and sandbox, or one per customer.
Use Test connection after saving credentials. It makes one real authenticated call, so you learn immediately rather than during a run at 3am.
Health and API changes
Connections are monitored. Repeated authentication failures mark a connection as needing attention, and you're emailed before every workflow using it starts failing.
YakPipes also keeps snapshots of each imported specification and tells you when an app's API changes — specifically flagging breaking changes like a removed operation or a newly required field. You can pin a workflow to a known-good version rather than being upgraded underneath you.
Still stuck? Email support@yakware.com and include the run id — it tells us exactly which step failed and why.