@devries-cameron20 / composio-1 / commits / 6b9c16661
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs: rewrite jira, linkedin, monday, notion, hubspot toolkit FAQs as questions

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Sushmithamallesh committed Feb 17, 2026 at 15:42 UTC 6b9c166611d1f5e4ee05ebbf05a008893e7b04fd
5 files changed +36 -35
docs/content/toolkit-faq/hubspot.md
+6 -4
@@ -2,8 +2,10 @@
2
3 For a step-by-step guide on creating and configuring your own HubSpot OAuth credentials with Composio, see [How to create OAuth credentials for HubSpot](https://composio.dev/auth/hubspot).
4
5 -## Query limits
6 -Use `limit <= 100` for `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` and `HUBSPOT_LIST_CONTACTS_PAGE` endpoints to avoid errors.
5 +## Why am I getting errors with `limit` on HubSpot contact searches?
6
8 -## Webhooks
9 -Webhooks require public apps (AppId + Developer API Key). Private/internal apps cannot receive HubSpot webhooks.
7 +The `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` and `HUBSPOT_LIST_CONTACTS_PAGE` tools have a maximum limit of 100 results per request. Set `limit` to 100 or lower to avoid errors.
8 +
9 +## Why can't I set up webhooks for HubSpot?
10 +
11 +HubSpot webhooks require a public app with an App ID and Developer API Key. Private or internal apps cannot receive webhooks.
docs/content/toolkit-faq/jira.md
+4 -5
@@ -2,9 +2,8 @@
2
3 For a step-by-step guide on creating and configuring your own Jira OAuth credentials with Composio, see [How to create OAuth credentials for Jira](https://composio.dev/auth/jira).
4
5 -## JQL GET vs POST and Search Issues
6 -- JQL GET and POST target the same search functionality but use different HTTP methods. POST supports complex queries in the request body.
7 -- Use the `fields` parameter to request specific fields; responses may include empty values if fields are undefined. Use `["*all"]` to request all fields.
5 +## What is the difference between JQL GET, JQL POST, and Search Issues?
6
9 -## Difference: JQL GET vs POST vs Search Issues
10 -Search Issues uses JQL POST under the hood and supports extra parameters/filters. For consistent results prefer POST when submitting complex queries.
7 +JQL GET and POST target the same search functionality but use different HTTP methods. POST supports complex queries in the request body. Search Issues uses JQL POST under the hood with extra parameters and filters. For consistent results, prefer POST for complex queries. Use the `fields` parameter to request specific fields, or `["*all"]` to request all fields.
8 +
9 +---
docs/content/toolkit-faq/linkedin.md
+9 -8
@@ -2,11 +2,12 @@
2
3 For a step-by-step guide on creating and configuring your own LinkedIn OAuth credentials with Composio, see [How to create OAuth credentials for LinkedIn](https://composio.dev/auth/linkedin).
4
5 -## LinkedIn rate limiting
6 -LinkedIn's default OAuth app is shared across users and has strict rate limits. Use a custom OAuth app for production to avoid shared quotas. Example error:
7 -```bash
8 -429 Client Error: Too Many Requests
9 -```
10 -
11 -## LinkedIn scope issue
12 -LinkedIn restricts certain scope combinations (e.g., `w_member_social` and `r_organization_admin` cannot be used together). If you need conflicting scopes, create your own OAuth app with the required permissions.
5 +## Why am I getting 429 rate limit errors on LinkedIn?
6 +
7 +The default OAuth app is shared across users and has strict rate limits. Use your own OAuth app for production to avoid shared quotas.
8 +
9 +## Why can't I use certain LinkedIn scope combinations?
10 +
11 +LinkedIn restricts certain scope combinations. For example, `w_member_social` and `r_organization_admin` cannot be used together. If you need conflicting scopes, create your own OAuth app with the required permissions.
12 +
13 +---
docs/content/toolkit-faq/monday.md
+5 -2
@@ -18,8 +18,9 @@ No. The admin only needs to install the app once per workspace. After that, any
18
19 For a step-by-step guide on creating and configuring your own Monday.com OAuth credentials with Composio, see [How to create OAuth2 credentials for Monday](https://composio.dev/auth/monday).
20
21 -## Monday has no scopes
22 -Note: Monday's authConfig does not accept scopes in the same way Google does. Scopes are configured on the OAuth app itself. When using the default OAuth app, ensure the required app-level scopes are configured for full toolkit access. If creating a custom app, add these scopes as needed:
21 +## How do I configure scopes for Monday.com?
22 +
23 +Monday.com doesn't accept scopes in the auth config the way Google does. Scopes are configured on the OAuth app itself. If you're using the default OAuth app, the required scopes are already configured. If creating your own app, add the scopes you need:
24
25 ```bash
26 me:read
@@ -42,3 +43,5 @@ teams:write
43 webhooks:write
44 webhooks:read
45 ```
46 +
47 +---
docs/content/toolkit-faq/notion.md
+12 -16
@@ -1,21 +1,17 @@
1 -## Notion Toolkit — FAQ
1 +## Why do Notion operations show "Composio" instead of the user's name?
2
3 -## Notion Operations show Composio instead of user’s name
4 -Why it happens: Notion attributes actions to the Integration itself (name/logo set in the Integration configuration), so operations and comments show the integration identity rather than the individual user.
5 -Fix: create and use your own Notion integration if you need a custom name/logo. See: https://developers.notion.com/docs/create-a-notion-integration
3 +Notion attributes actions to the integration itself, not the individual user. The name and logo shown come from the integration configuration. To use a custom name or logo, create your own Notion integration. See [Notion integration docs](https://developers.notion.com/docs/create-a-notion-integration).
4
7 -## Granting access to more pages
8 -If you initially granted access to specific pages and later need to add more:
9 -1. Open Notion → Settings & Members → Connections
10 -2. Select the integration (Composio or your custom integration)
11 -3. Click "Select pages" (or "Manage access") and add/remove pages as required
5 +## How do I grant access to more Notion pages?
6
13 -## Notion has no scopes
14 -Notion does not use OAuth scopes. Instead, integrations are granted access to specific resources (pages/databases) during the authorization flow or via integration settings. You do not need to pass scopes when creating an authConfig.
7 +Open Notion, go to Settings & Members, then Connections. Select the integration (Composio or your custom integration), click "Select pages" or "Manage access", and add or remove pages as needed.
8
16 -## Configuring Scopes / Access model
17 -Notion access is controlled by the integration type:
18 -- OAuth app (public): access selection happens at authorization time.
19 -- Internal integration (API key): page access is managed in the Integration settings.
20 -Choose the integration model that matches your deployment and permissions needs.
9 +## Does Notion use OAuth scopes?
10
11 +No. Notion controls access by granting integrations access to specific pages and databases, not through scopes. You don't need to pass scopes when creating an auth config.
12 +
13 +## How does Notion's access model work?
14 +
15 +It depends on the integration type. OAuth apps (public) let users select which pages to share during authorization. Internal integrations (API key) have page access managed in the integration settings.
16 +
17 +---