Connectors (Marketplace)
The connector marketplace centralises the integrations between FoxPlan and your external tools (messaging, CRM, ERP, ITSM, HR). Each connector is installed on a workspace, configured once, then automatically reacts to FoxPlan business events (status change, assignment, comment…).
Settings → Connectors
The Connectors screen is reserved for workspace or company administrators, like the rest of the Settings menu. It has two tabs: the Marketplace (outbound connectors) and API (API accounts, Swagger documentation, request log). The marketplace is a feature being rolled out: FoxPlan opens the whole catalog or only some connectors to your instance, and you only see the ones opened to you — until any is, the tab says so. To request access, contact your FoxPlan representative.
Catalogue
| Connector | Vendor | Categories | Maturity |
|---|---|---|---|
| Slack | Slack | Communication, Notifications | Stable |
| Microsoft Teams | Microsoft | Communication, Notifications | Stable |
| Google Chat | Communication, Notifications | Stable | |
| Jira Cloud | Atlassian | ITSM, Project management | Beta |
| HubSpot | HubSpot, Inc. | CRM, Marketing | Alpha |
| Odoo | Odoo S.A. | ERP, Open Source | Alpha |
| Pennylane | Pennylane | Finance, Accounting | Alpha |
| Sage Business Cloud Accounting | Sage Group plc | Finance, Accounting | Alpha |
| Cegid | Cegid | ERP, Finance, HR | Alpha |
| HiBob | Hibob | HR, People | Alpha |
| Infor M3 | Infor | ERP, Manufacturing | Alpha |
| SAP S/4HANA Cloud (Public) | SAP SE | ERP, Finance | Alpha |
| Zapier | Zapier | Middleware, iPaaS, Automation | Beta — standard |
| Make | Celonis (Make.com) | Middleware, iPaaS, Automation | Beta — standard |
| n8n | n8n | Middleware, iPaaS, Automation | Beta — standard |
| Microsoft Power Automate | Microsoft | Middleware, iPaaS, Automation | Beta — standard |
| Workato | Workato | Middleware, iPaaS, Automation | Beta — standard |
- Stable: production-ready.
- Beta: functional, scope may still change.
- Alpha: bootstrap connector (connection test + one flow). Evaluation only.
Installing a connector
- Open Settings → Connectors.
- Click the card of the connector you want to open its page.
- Configuration tab: fill in the required fields (URL, tokens, credentials…).
- Click Save. The connector is then installed on the workspace.
- Use Test to check the connection before enabling the flows.
The toggle at the top of the page enables / disables the whole installation without losing its configuration.
Configuration fields
The pages use typed fields: text, URL, number, boolean, list, text area, password and secret. Fields flagged as secret (API tokens, signed webhook URLs…) are encrypted at rest and are never displayed again in clear text — a mask (••••) shows that a value is already stored.
Authentication depends on the connector: incoming webhook URL (chat), API token, Bearer, Basic or OAuth depending on the target tool.
Flows and triggers
A connector exposes one or more flows. Each flow is enabled independently in the Flows tab of its page.
Messaging connectors (Slack, Teams, Google Chat) and iPaaS middlewares offer six flows, reacting to the following events:
| Flow | Events |
|---|---|
| Task notifications | status, owner (assignment) or planning allocation change |
| Comment notifications | comment added to a task |
| Task progress | change of a task's completion percentage |
| Project objects | creation, update or deletion of a risk, decision, requirement, change, file or project weather report |
| Support tickets | creation of a Support ticket and status change |
| Comments on objects | comment added to a project object or a Support ticket |
The first two flows (tasks and task comments) only fire if the matching project notification options are enabled (Notify on status change, Notify on assignment, Notify on comment…), set in Project definition. A freshly installed connector therefore stays silent on those two flows until the options are ticked on the projects concerned.
The four other flows (progress, project objects, Support tickets, comments on objects) do not depend on any project option: enabling the flow in the connector is enough.
Manual trigger
On-demand flows (a synchronisation, for example) can be started manually with the Run now button in the Flows tab. The outcome (success / failure, HTTP code) is returned immediately.
iPaaS middleware (Zapier, Make, n8n, Power Automate, Workato)
Five connectors to no-code automation platforms ship as standard on every instance: they appear in Settings → Connectors for your administrators, with no access request. They work in both directions — outbound JSON events by webhook, inbound actions through the REST API (API tab of the connector page) — and can only act on the instance they are attached to.
Setup tool by tool, the format of the event sent and the API catalogue are described on the dedicated page: iPaaS middleware.
Monitoring and logs
The Logs tab of each connector lists the latest executions: date, flow, event type, status, HTTP code, duration and message.
- Sending to external tools is asynchronous: it never impacts saving the task in FoxPlan. If a connector fails, the FoxPlan action still completes and the error is logged.
- Logs are purged automatically after a retention period (60 days by default), handled by a MongoDB TTL index.
Slack / Teams / Google Chat webhook URLs entered directly on the project record keep working as before, alongside the connectors. Marketplace connectors do not replace them: they offer a centralised, workspace-wide configuration.
Security
- All connector secrets are encrypted (AES-GCM) with a dedicated key (
CONNECTOR_SECRETS_ENCRYPTION_KEY). - Connector data (installations, flow configuration, logs) is partitioned per workspace (tenant).
- Access to the screen is restricted to FoxPlan accounts, and the matching API calls are protected server-side.