Integrations
Project context and task references for internal assistants. Configure credentials in the FlexyAgents dashboard, scope knowledge and channels per agent, and test in staging before production traffic.
Asana connects FlexyAgents to your existing stack under the "Productivity" category. Exact OAuth scopes, field mappings, and plan availability evolve with the product—use the dashboard as the source of truth after this orientation.
General pattern: authorize the integration at the organization level, select what to sync or which channel resource to bind, attach the resulting knowledge or channel to an agent, then validate with test conversations and automations.
This integration feeds FlexyAgents structured or unstructured data so retrieval can answer with fresh context. Sync jobs may run on a schedule; monitor failures in the dashboard.
If your use case spans multiple systems (e.g., Shopify plus Zendesk), attach multiple integrations to complementary knowledge bases and keep agent instructions explicit about precedence.
Create or choose a dedicated integration account when possible so employee offboarding does not break production sync.
Record which environments (staging vs production) use which credentials; never reuse production tokens in lower environments without understanding data bleed risk.
After first connection, run a small test corpus or sandbox channel before exposing to customers.
Apply least-privilege OAuth scopes. Rotate secrets on the same schedule as other third-party keys.
Document subprocessors and data categories in your internal security packet; export conversation samples only under policy.
Auth errors usually mean expired tokens or changed passwords—reauthorize and replay sync.
Empty answers may indicate the agent is not attached to the knowledge base or channel you expect; re-check bindings.
See Documentation → Troubleshooting for cross-cutting issues like CSP or model keys.
继续探索
平台功能 · HTTP API 与 Webhook · 快速开始 · 联系