Connectors, Modules, and App Integrations
Connectors and Modules
Fusion offers connectors for many apps (Workfront, Google Workspace, Microsoft 365, Slack, etc.). Each connector provides modules for specific actions: triggers (watch for new data), actions (create/update), and searches (find records). Universal connectors (HTTP, Webhooks) allow custom integrations. When using a connector, you must establish a connection with proper authentication (OAuth, API key, etc.).
Module Configuration
- Triggers: Configure polling interval or webhook URL.
- Actions: Map required fields; some fields are mandatory.
- Searches: Define search criteria and output limits.
- Transformers: Built-in modules for data manipulation (e.g., text parser, aggregator).
Traps in Questions
- Connection permissions: The connection's user must have access to the data; insufficient permissions cause errors.
- Rate limits: Apps may throttle requests; Fusion handles retries but excessive calls can fail.
- Module versions: Different versions may have different fields; always check the version.
- Trigger types: "Watch" modules are polling; "Instant" triggers use webhooks. Confusing them leads to scheduling mistakes.
Worked Example / Rule of Thumb
Rule of thumb: "Match the module to the task: Watch for triggers, Create/Update for actions, Search for lookups." For example, to sync Workfront projects to Asana, use a Workfront "Watch Projects" trigger and an Asana "Create Task" action, mapping project name to task name.