When Does Integration Make Sense?
If tasks arrive in SimpleBoard from external sources — helpdesk tickets, CRM deals, form submissions, GitHub pull requests — manually copying information between systems is a waste of time and a source of errors. Every time someone has to copy a ticket number, a client name, or a task description from one tool into another, there's a chance for information to get lost or corrupted.
Integrations solve this by automating the handoff. A new support ticket becomes a card. A won deal in your CRM creates a client board. A merged pull request moves a card to "Done." The information flows automatically, and your team works in the board without having to babysit other tools.
How It Works
SimpleBoard exposes two integration mechanisms that cover most use cases:
- API (you call SimpleBoard) — your script or service makes HTTP requests to the SimpleBoard REST API to create cards, move them between columns, add time entries, update labels, and more. This is the right approach when you want to push data into SimpleBoard from an external event.
- Webhooks (SimpleBoard calls you) — SimpleBoard sends an HTTP POST to your endpoint whenever something happens in the board: a card is created, moved, completed, or commented on. This is the right approach when you want to react to board events in an external system.
Think of it as API = pull, webhook = push. Most integrations use both: a webhook fires an event, your script processes it and calls the API to take an action.
Use Case 1: Helpdesk — Auto-Create Cards from Tickets
Your support team lives in a helpdesk tool. Every new ticket that needs developer attention currently gets copy-pasted into the board by hand. With the API, you can eliminate that entirely.
The flow: new ticket created in helpdesk → helpdesk fires a webhook to your script → script calls the SimpleBoard API → card appears in the "TODO" column with the ticket title, number, and a link back to the helpdesk ticket.
curl -X POST https://api.simpleboard.pl/v1/boards/brd_01j9xk2m/cards \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"title": "Ticket #4821 — user locked out", "column_id": "col_todo"}' Getting your API key: Go to Settings → API → New key. Give the key a descriptive name (e.g., "helpdesk-integration"), copy it, and store it securely — it won't be shown again. Full endpoint documentation is available at /en/api-reference.
Once the card is created, your team can move it through the board normally — no copy-pasting, no missed tickets, no duplicate entries.
Use Case 2: CRM — New Client, New Board
When a deal is marked "Won" in your CRM, there's usually a burst of onboarding work to kick off: set up accounts, send welcome emails, schedule kickoff calls, create internal tracking. This is repetitive work that looks identical for every new client.
With the API, you can automate the entire setup: deal marked "Won" → CRM webhook fires → your script creates a new SimpleBoard board named after the client → a set of standard onboarding cards is created in the "TODO" column from a template. Your team opens the board and all the standard tasks are already there, ready to be assigned and worked.
This works especially well for agencies and consulting teams where client onboarding follows a consistent checklist. You stop creating boards manually and start every engagement from a consistent, complete starting point.
Use Case 3: GitHub — Merge Equals Done
For product teams that track development work on SimpleBoard boards, keeping card status in sync with actual code status is a constant challenge. The fix is simple: configure a GitHub webhook to fire on pull_request events, check whether the PR was merged to main, find the matching SimpleBoard card by title or a reference in the PR description, and move it to the "Done" column via the API.
The result: when a developer merges a PR, the card moves automatically. No one has to remember to update the board. Status is always accurate without manual intervention.
Use Case 4: Contact Forms
Contact form submitted on your website → webhook fires → card created in SimpleBoard's "TODO" column with the client's name, email, and message in the card description. Your sales or support team sees new leads appear in the board in real time, with all the relevant information already there.
This works with any form tool that can fire a webhook — Typeform, Tally, a custom HTML form with a serverless function, or a no-code automation like Make or Zapier triggering the SimpleBoard API.
Webhook Payload Example
When SimpleBoard fires a webhook, the payload looks like this:
{
"event": "card.created",
"card_id": "crd_xyz123",
"card_title": "Ticket #4821 — user locked out",
"board_id": "brd_01j9xk2m",
"column_id": "col_todo"
} The payload includes the event type, the IDs of the affected card, board, and column, and the card title. Your endpoint can use these to look up additional details via the API, route the event to the right handler, or log it for debugging.
Getting Started
Three steps to connect SimpleBoard to your other tools:
- 1. Generate an API key in Settings → API → New key. Keep it secret — treat it like a password.
- 2. Read the API reference at /en/api-reference. Every endpoint is documented with request and response examples. You can test calls directly from the docs page.
- 3. Configure webhooks in Settings → Webhooks. Enter your endpoint URL, choose which events to subscribe to, and save. SimpleBoard will start sending POST requests to your endpoint immediately.
If you run into questions or want help designing a specific integration, reach out at hello@simpleboard.pl — we're happy to help think through the right approach for your setup.