Integrations

The project Integrations tab connects one project to other systems:

• Outgoing webhooks push project events (task created, sprint started, document created…) to an HTTPS endpoint you own, signed so the receiver can trust them.
• Incoming webhook tokens let an outside system (a form tool, GitHub, a script) create tasks or comments in the project.
• Public API tokens give another system scoped, read or write access to the project's tasks and time through the SolaProjects API.
• Native provider readiness shows ready-made connections (Slack, Microsoft Teams, GitHub, GitLab, Google Calendar, Google Drive, OneDrive, Zapier / IFTTT) and whether each can be connected.

Use it when a project needs to talk to another tool — for example to post task updates to a client dashboard, or to turn website enquiries into tasks. Project managers and administrators set it up; it is usually done once per project with your IT contact.

Two pages are called Integrations. This page covers the project tab. The Integrations item in the Workspace part of the sidebar (/projects/settings/integrations) is the organization's SolaCount connection — see Organization SolaCount connection below and Budget and finance.

Where to find it

Who sees it:

• Plan: integrations are a Premium-plan feature (also Enterprise). On lower plans the tab is hidden. If a paid plan lapses, the tab disappears and webhooks stop being offered until you renew.
• Role: only people who can edit the project can load the tab (see Permissions). Others see "We couldn’t load integrations." with Retry.

Screen tour

Header card

Integrations — Outgoing webhooks, incoming tokens, and delivery history.

Outgoing webhooks card

POST project events to an external HTTPS endpoint, signed with HMAC-SHA256. New webhook at the top-right.

Each webhook card shows the name, endpoint URL, a status badge (Active, Disabled or Archived), one chip per subscribed event, and {n} deliveries · {n} failed. Row actions (not on archived webhooks): Edit, Test, Rotate secret, Archive.

Empty state: No outgoing webhooks — Create one to push events to an external system.

Incoming webhook tokens card

Let external systems create tasks/comments by POSTing with a secret token. New token at the top-right.

Each token card: name, provider (Custom or GitHub) · last used {date} or never used, badge Active, Inactive or Revoked. Actions (not on revoked tokens): Rotate, Revoke.

Empty state: No incoming tokens — Create a token to accept inbound webhooks.

Public API card

Create scoped bearer tokens for documented project, task and time-entry endpoints. Buttons: Docs (opens the OpenAPI reference in a new tab) and New token.

Each token card: name, last used {date} / never used, status badge, one chip per ability. Actions: Rotate, Revoke.

Empty state: No API tokens — Create a token for the public API.

Recent deliveries card

Outgoing delivery attempts and their outcome. Badge with the count.

Empty state: No deliveries yet — Delivery attempts appear here once an event fires or you send a test.

Native provider readiness card

Connection state and setup prerequisites for provider-specific integrations. One tile per provider:

Each tile shows a status (Available, Pending, Active, Failed), the capability, and either Live provider configuration detected. or Local simulator is available; production credentials are activation settings. (the provider is not yet live for your organization). It may also show Blocked by missing setup: …, Activation notes: …, OAuth callback pending., Last error: …, the last message or last event received.

Events you can send

Tick one or more on the webhook form:

Each request is a JSON POST with headers X-SolaProjects-Event (event type), X-SolaProjects-Delivery (delivery id) and X-SolaProjects-Signature (HMAC-SHA256 of the raw body with your signing secret), and User-Agent: SolaProjects-Webhooks/1.0. Verify the signature before trusting a request.

Retries. A failed delivery is retried automatically after about 1, 5, 15 and 60 minutes; after the fifth attempt it stays Failed. Use Retry to try again by hand.

Tasks

Create an outgoing webhook

1. Open the project → Integrations → New webhook.

2. Fill in New outgoing webhook:

   Field	Required	Rules / defaults	Notes
   Name	Yes	Up to 160 characters.	e.g. Client dashboard.
   Endpoint URL (HTTPS)	Yes	Valid URL, up to 2,048 characters, public HTTPS.	Placeholder https://example.com/hooks/solaprojects. Local and private-network addresses are refused: "Use a public HTTPS endpoint. Local and private network URLs are blocked."
   Events	Yes	At least one.	See the table above.
   Active	—	Ticked by default.	Untick to save it Disabled.

3. Click Create. You see Outgoing webhook created. and the Signing secret dialog: "Store this now — it is shown only once and cannot be retrieved later." Click Copy (Copied to clipboard.), store the secret in the receiving system, then Done.

Edit, test, rotate and archive a webhook

Create an incoming webhook token

1. Click New token on Incoming webhook tokens.
2. Name (required, up to 160 characters) and Provider: Custom (default) or GitHub.
3. Click Create → Incoming token created. Copy the Incoming webhook token shown once: "Use this as the token in your incoming webhook URL. Shown only once."

The external system then sends POST /api/projects/webhooks/incoming/{token} with a JSON body (limit 60 requests per minute per sender):

Anything else is refused with "Webhook rejected."; a revoked or wrong token gets the same answer. Tasks and comments are authored by the person who created the token.

Rotate issues a new token and revokes the old one immediately (Token rotated.). Revoke asks Revoke token — "Requests using this token will no longer have access." → Token revoked.

Create a public API token

1. Click New token on Public API.

2. Name (required, up to 120 characters) and Abilities (at least one; projects:read, tasks:read and time:read are pre-ticked):

   Ability	Allows
   projects:read	Read this project.
   tasks:read / tasks:write	Read / create and update tasks.
   time:read / time:write	Read / create time entries.

3. Create → API token created. Copy the Project API token: "Use this as a Bearer token for /api/v1. Shown only once."

Tasks created through the API fire the same automations and webhooks as tasks created in the app. Rotate → confirm Rotate token ("The current token will stop working. Update connected services with the new token.") → API token rotated. Revoke → API token revoked.

Retry a failed delivery

In Recent deliveries, click Retry on the row → Delivery retried. Check Status and Response after a moment.

Connect a native provider

1. On the provider tile pick the channel (e.g. #projects for Slack) and click Connect → {Provider} connection started.
2. Complete the authorization dialog {Provider} authorization with Complete callback (or Later) → Native integration connected.
3. Once connected, use Send test ({Provider} test message sent.), Refresh ({Provider} refreshed.) or Disconnect ({Provider} disconnected.).

Tiles in simulator mode also show Simulate event and Error for checking the setup before the provider goes live; they do not contact the real service.

Statuses

Permissions

If integration editing is switched off for your organization, the tab is read-only (no New, row actions or Retry). A refused change shows "Integration edits are disabled or not permitted."; a stale page "Please reload and try again." Secrets and tokens are never shown again after the one-time dialog — not even to owners.

Organization SolaCount connection

The Workspace sidebar item Integrations (/projects/settings/integrations) is a different page. It shows whether SolaProjects is connected to SolaCount (Connected, Ready to connect, Integration paused, Disconnected — history preserved, …), and lets an organization owner or Finance administrator connect, pause, disconnect or check the connection. A single project can opt out on its Settings tab (Integrations card → Internal project / finance disabled). See Budget and finance and the SolaProjects overview.

Worked examples

Example 1 — Enquiries become tasks (everyday)

Sara Khan wants website enquiries for Al Noor Showroom Fit-out (ALN-FIT) to land as tasks.

1. New token → Name Website enquiries, Provider Custom → Create; she gives the token to the web developer.
2. The website posts {"title": "Quote request – reception desk", "priority": "high"}.
3. Task ALN-31 Quote request – reception desk appears in Todo, private, priority High. The token card shows last used Oct 6.

Example 2 — Client dashboard feed with a failure (full scenario)

Omar Haddad connects Al Noor Trading LLC's site dashboard.

How it connects

Tips and common problems

Related

• Automations · Tasks · Planning
• Settings · Budget and finance · Guest share links
• Time approval & billing · SolaProjects overview
• Projects in SolaCount