Apps
The 40+ prebuilt connections in Settings → Apps — one-click setup, what they do, and which data goes where.
The Settings → Apps (Ayarlar → Uygulamalar) page is the catalog of prebuilt connections. Each card has a details page (overview, setup steps, permissions, link to docs); the Install (Kur) button starts setup — for most apps the provider's consent screen opens, and you don't copy any keys or URLs. Connected apps are grouped on the Connected (Bağlı) tab, which shows the result of the latest delivery.
Connections work in four modes:
| Mode | What happens | Example |
|---|---|---|
| Channel | CRM events are posted as messages to a channel. | Slack, Teams, Telegram |
| Record from event | A CRM event creates a record in another app. | Notion page, Asana task, Sheets row |
| Record action | A one-click action from the Apps (Uygulamalar) menu on a record page. | Find an email with Hunter, call with Aircall, create a PandaDoc document |
| Inbound data | An external system sends data to the CRM. | Website form, Stripe, Segment |
For connections that send events, you choose which events are sent; the event list and payload format are on the Webhooks page. Accounting and ERP connections (Paraşüt, Logo, SAP…) are in the Accounting & ERP category of the catalogue and are set up on their own page: Accounting & ERP.
Setup
The app page tells you which path applies (One-click setup / Guided setup).
| Path | Apps | What you do |
|---|---|---|
| One click (consent screen) | Slack, Microsoft Teams, Discord, Google Sheets, Notion, Asana, ClickUp, Airtable, Linear, Mailchimp, Typeform, Calendly, PandaDoc, Apollo | Install (Kur) → on the provider's consent screen, choose your account (and, for Slack and Discord, the channel) and allow access. |
| Central bot | Telegram | Install → Add to group (Gruba ekle) → choose the group in Telegram; when the bot joins, the connection is made and a confirmation message is posted. For a channel, make the bot an admin and post the /baglan command shown on the page. |
| Guided (one key) | Stripe, Aircall, lemlist, Tally, Resend, Hunter, Mixmax — and the apps above on installations without the consent screen | Install → Open the key page to create an API key at the provider → paste it and Connect (Bağla). The key is tested and your account is shown. |
After setup:
- Choosing a destination — where needed, you choose where to write when you return: team and channel in Teams, project in Asana, list in ClickUp, base and table in Airtable (title, notes, and link fields from the schema), team in Linear, audience in Mailchimp, form in Typeform / Tally, campaign in lemlist, template in PandaDoc, sender domain in Resend. A single option is selected automatically. In Notion, a CRM events database is created in the page you shared; in Google Sheets, the spreadsheet is created in your Drive.
- Webhooks created for you — in Typeform, Tally, Calendly, Stripe, lemlist, and Aircall, the CRM's inbound URL is registered with the provider together with a signing secret. Regenerate URL (Adresi yenile) also renews the webhook, and removing the connection deletes it at the provider.
- Confirmation message — Slack, Teams, and Discord get a "connected" message in the channel; in Slack the
/crmcommand works without extra setup. - Token refresh — access tokens are refreshed automatically before delivery. If access is revoked at the provider, the connection card shows a warning and Reconnect (Yeniden bağla); reconnecting keeps your selections and events.
- Set up manually (Elle ayarla) — the link on every setup page opens the old path (webhook URL, key, and ID fields), for using your own Slack app or your own bot.
On a self-hosted installation, register your own app with the provider for one-click setup and set <PROVIDER>_CLIENT_ID / <PROVIDER>_CLIENT_SECRET in .env (for Google and Microsoft, the existing GOOGLE_* / MS_*); the redirect URL is the installation's /account/email/oauth/callback.
Catalog
| App | Mode | What it does |
|---|---|---|
| Slack | Channel · command | Selected events are posted to a channel; the /crm command searches companies, people, and opportunities from Slack. |
| Microsoft Teams | Channel | Events are posted to a Teams channel as cards. |
| Google Chat | Channel | Events are posted to a Google Chat space as messages. |
| Discord | Channel | Events are posted to a Discord channel. |
| Telegram | Channel | A Telegram bot posts events to a group or channel. |
| Webhook | Event | Signed JSON to any URL. |
| Zapier · Make · n8n · Pipedream | Event + API | Events trigger your workflow; the workflow writes back to the CRM with an API key. |
| Notion | Record from event | Events are added as pages to a Notion database. |
| Airtable | Record from event | Events are added as rows to an Airtable table. |
| Google Sheets | Record from event | Events are added as rows to a spreadsheet (date · event · title · description · link). |
| Asana · ClickUp | Event + action | Creates tasks from events and records. |
| Linear | Action | Creates a Linear issue from a support ticket or note. |
| Productboard | Action | Sends customer feedback (notes, requests) as insights. |
| PandaDoc | Action | Creates a PandaDoc document from a quote and sends it for signature. |
| Stripe | Action + inbound | The company's Stripe customer and invoices; payments appear on the timeline. |
| Aircall | Action + inbound | One-click calling from a person; calls are logged as activities, calls with a recording go to Calls with transcript and summary, missed calls become callback tasks; a CRM card shows in Aircall while the call rings. |
| RingCentral | Action + inbound | Calling with the RingCentral app; call records become activities via Zapier, and calls with a recording go to Calls. |
| Calendly / Cal.com | Inbound | Bookings land on the calendar, the person, and a note; a cancellation cancels the meeting. |
| Meeting notes | Inbound | Circleback, Fireflies, Granola: transcript and notes go to Calls, a note to the company, action items become tasks. |
| Segment | Inbound | People, companies, and notes from identify / group / track events. |
| Data sync | Inbound | Bulk-creates and updates companies / people from a data warehouse. |
| Website form · Typeform · Tally | Inbound | Submission → prospect company + person + task for the owner. |
| Apollo | Action | Enriches a company from its domain and a person from their email. |
| Hunter | Action | Finds / verifies emails; fetches the people at a domain. |
| Mailchimp · Brevo · MailerLite · ActiveCampaign | Event + action + sync | New people join the list / audience automatically, existing people with Sync audience now (scope: all people, contacts of active customers or of prospects). Unsubscribed people and people who left the company are never sent, and someone who unsubscribed in the tool is not resubscribed; unsubscribes in the tool are pulled into the CRM's email block list twice a day, so CRM sequences skip them too. |
| lemlist | Action + inbound | Adds a person to a campaign; reply and interest events become notes and tasks. |
| Mixmax | Action | Adds a person to a Mixmax sequence. |
| Resend | System | Notification and invitation emails are sent through Resend; people are added to a Resend audience. |
| Amazon SES | System | Notification and invitation emails are sent through Amazon SES (SES API v2); the test shows the quota and domain verification. Email sending |
| Okta / Entra ID (SCIM) | Inbound | Users are created, updated, and deactivated from the identity provider. SCIM |
| Add from browser | Action | Bookmarklet: adds the company on the page you're viewing (website, LinkedIn, Gmail) as a prospect. |
| Google Drive · OneDrive · Dropbox | Storage | Record files go to a CRM folder in the cloud. Storage |
| Cloud backup | Storage | The daily database backup is also sent to the connected cloud account. |
| Claude | AI | Connects the CRM to Claude (MCP). MCP |
Apps on record pages
On company, person, opportunity, and support ticket pages, the Apps (Uygulamalar) menu shows actions from connected apps: call with Aircall, find an email with Hunter, enrich with Apollo, create an Asana task, create a PandaDoc document… The external record created in the app (task, page, document) is written to the CRM record along with its link, and opens from the same menu.
If a calling app is connected, a Call (Ara) button appears next to person and company phone numbers; after the call, an activity is logged automatically.
Requesting an app
Need an app that isn't in the catalog? The Request an app (Uygulama isteyin) link at the bottom of the Apps page sends your request to the Solk team; the most-requested apps are prioritized. In the meantime, you can connect almost any tool with webhooks, inbound hooks, and the REST API.
Security
- For connections set up through the consent screen, the provider app's client secret is not on the installation: the code → token exchange and refreshes happen in the Solk panel; the installation stores only the access token for your account and an encrypted refresh token.
- App keys you paste are stored only in the installation's own database and are masked on screen; OAuth tokens for storage accounts and email passwords are stored encrypted. Protect your database backups accordingly.
- Only admins can set up connections (except storage accounts and Claude — each user connects those for themselves).
- Each connection's card shows its latest delivery, error, and counter; the Test connection (Bağlantıyı dene) button verifies the credentials (for form and booking apps with a webhook, the account).