langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Notion tools do not support status properties #711

New Issue
Closed
opened 2026-02-16 10:20:15 -05:00 by yindo · 7 comments
yindo commented 2026-02-16 10:20:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @aflatter on GitHub (Oct 13, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I'd like to query a Notion database to provide context to my application. The database uses a status property. The records are successfully returned by the tools but the status property is always returned as <status>, so I don't have access to the actual value.

2. Additional context or comments

It seems that both of these tools don't support the status field as there's no handling for it, e.g. in https://github.com/langgenius/dify-official-plugins/blob/main/tools/notion/tools/query_database.py#L73

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @aflatter on GitHub (Oct 13, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify-official-plugins/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. I'd like to query a Notion database to provide context to my application. The database uses a status property. The records are successfully returned by the tools but the status property is always returned as `<status>`, so I don't have access to the actual value. ### 2. Additional context or comments It seems that both of these tools don't support the status field as there's no handling for it, e.g. in https://github.com/langgenius/dify-official-plugins/blob/main/tools/notion/tools/query_database.py#L73 ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the bugenhancement labels 2026-02-16 10:20:15 -05:00
yindo closed this issue 2026-02-16 10:20:16 -05:00
yindo commented 2026-02-16 10:20:16 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 13, 2025):

Hi @aflatter! I'm Dosu and I’m helping the dify-official-plugins team.

You're right—the Notion tools in dify-official-plugins don't currently support the status property. In the code (query_database.py), only certain property types are handled (like title, select, multi_select, etc.), and anything else—including status—just returns <status> as a placeholder.

To fix this, you’d need to add a new condition for status in the property extraction logic, similar to how select is handled. For example:

elif prop_type == "status":
    status_data = prop_data.get("status", {})
    value = status_data.get("name") if status_data else None

This would let you access the actual status value from your Notion database queries. There’s an open feature request for this (issue #1848), and a related bug report (dify/issues/1542), so you can track progress or add feedback there.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Oct 13, 2025): <!-- Greeting --> Hi @aflatter! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify-official-plugins team. <!-- Answer --> You're right—the Notion tools in dify-official-plugins don't currently support the status property. In the code ([query_database.py](https://github.com/langgenius/dify-official-plugins/blob/9fd29b976c4d377567b0af07d80de51c452921a0/tools/notion/tools/query_database.py)), only certain property types are handled (like title, select, multi_select, etc.), and anything else—including status—just returns `<status>` as a placeholder. To fix this, you’d need to add a new condition for `status` in the property extraction logic, similar to how `select` is handled. For example: ```python elif prop_type == "status": status_data = prop_data.get("status", {}) value = status_data.get("name") if status_data else None ``` This would let you access the actual status value from your Notion database queries. There’s an open feature request for this ([issue #1848](https://github.com/langgenius/dify-official-plugins/issues/1848)), and a related bug report ([dify/issues/1542](https://github.com/langgenius/dify/issues/1542)), so you can track progress or add feedback there. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/895e0247-ae8a-4e6b-a928-8ee859e1973a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/895e0247-ae8a-4e6b-a928-8ee859e1973a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/895e0247-ae8a-4e6b-a928-8ee859e1973a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/895e0247-ae8a-4e6b-a928-8ee859e1973a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/895e0247-ae8a-4e6b-a928-8ee859e1973a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/895e0247-ae8a-4e6b-a928-8ee859e1973a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/895e0247-ae8a-4e6b-a928-8ee859e1973a?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/1848)
yindo commented 2026-02-16 10:20:16 -05:00
Author
Owner
Copy Link
Copy Source

@aflatter commented on GitHub (Oct 13, 2025):

FWIW this also applies to relation properties which appear as <relation> only.

@aflatter commented on GitHub (Oct 13, 2025): FWIW this also applies to relation properties which appear as `<relation>` only.
yindo commented 2026-02-16 10:20:16 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 13, 2025):

You're correct—relation properties aren't currently supported either and show up as <relation> in query results. This is a known limitation in the code: only certain property types are handled, and anything else (including relation and status) falls back to a placeholder string. There are open issues and user reports confirming this behavior (example).

To support relation properties, the extraction logic in query_database.py would need a new condition for relation, similar to how multi_select is handled. You'd typically extract the list of related page IDs (or URLs) from the relation field in the property data instead of just returning <relation> (code reference).

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Oct 13, 2025): <!-- Answer --> You're correct—relation properties aren't currently supported either and show up as `<relation>` in query results. This is a known limitation in the code: only certain property types are handled, and anything else (including relation and status) falls back to a placeholder string. There are open issues and user reports confirming this behavior ([example](https://github.com/langgenius/dify-official-plugins/issues/1425)). To support relation properties, the extraction logic in `query_database.py` would need a new condition for `relation`, similar to how multi_select is handled. You'd typically extract the list of related page IDs (or URLs) from the `relation` field in the property data instead of just returning `<relation>` ([code reference](https://github.com/langgenius/dify-official-plugins/blob/9fd29b976c4d377567b0af07d80de51c452921a0/tools/notion/tools/query_database.py)). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/805e441f-cef6-4fdb-a4e6-437eed3f5d4d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/805e441f-cef6-4fdb-a4e6-437eed3f5d4d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/805e441f-cef6-4fdb-a4e6-437eed3f5d4d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/805e441f-cef6-4fdb-a4e6-437eed3f5d4d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/805e441f-cef6-4fdb-a4e6-437eed3f5d4d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/805e441f-cef6-4fdb-a4e6-437eed3f5d4d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/805e441f-cef6-4fdb-a4e6-437eed3f5d4d?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/1848)
yindo commented 2026-02-16 10:20:16 -05:00
Author
Owner
Copy Link
Copy Source

@aflatter commented on GitHub (Oct 14, 2025):

Potentially useful for others: My current work-around is to combine this plugin with Notion-MCP.

  1. The plugin supports listing pages in a database which Notion-MCP does not (it can only do search)
  2. The plugin does not have full support for properties, so I do a fetch call via Notion-MCP for each page in the database.
@aflatter commented on GitHub (Oct 14, 2025): Potentially useful for others: My current work-around is to combine this plugin with Notion-MCP. 1. The plugin supports listing pages in a database which Notion-MCP does not (it can only do search) 2. The plugin does not have full support for properties, so I do a `fetch` call via Notion-MCP for each page in the database.
yindo commented 2026-02-16 10:20:16 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 30, 2025):

Hi, @aflatter. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that the Notion tools in dify-official-plugins do not properly support status properties, returning "" instead of actual values.
  • The current code only handles certain property types, missing support for status and relation properties.
  • You shared a workaround by combining this plugin with Notion-MCP to get full property details.
  • Related open issues are tracking these feature gaps, but no resolution has been implemented yet.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here.
  • If I don’t hear back within 5 days, I will automatically close this issue.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Oct 30, 2025): Hi, @aflatter. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that the Notion tools in dify-official-plugins do not properly support status properties, returning "<status>" instead of actual values. - The current code only handles certain property types, missing support for status and relation properties. - You shared a workaround by combining this plugin with Notion-MCP to get full property details. - Related open issues are tracking these feature gaps, but no resolution has been implemented yet. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here. - If I don’t hear back within 5 days, I will automatically close this issue. Thanks for your understanding and contribution!
yindo commented 2026-02-16 10:20:16 -05:00
Author
Owner
Copy Link
Copy Source

@aflatter commented on GitHub (Oct 30, 2025):

Still relevant.

@aflatter commented on GitHub (Oct 30, 2025): Still relevant.
yindo commented 2026-02-16 10:20:16 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 15, 2025):

Hi, @aflatter. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that the Notion tools do not properly support status and relation properties, showing placeholders instead of actual values.
  • It was confirmed that the current code only handles certain property types, lacking support for status and relation.
  • You shared a workaround using Notion-MCP to fetch full property details.
  • No fix has been implemented yet, and the issue remains open and relevant.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here.
  • If I do not hear back within 5 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Nov 15, 2025): Hi, @aflatter. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that the Notion tools do not properly support status and relation properties, showing placeholders instead of actual values. - It was confirmed that the current code only handles certain property types, lacking support for status and relation. - You shared a workaround using Notion-MCP to fetch full property details. - No fix has been implemented yet, and the issue remains open and relevant. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here. - If I do not hear back within 5 days, I will automatically close this issue. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label bug enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#711
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?