https://linen.dev logo
API Schema Completeness Issue - Trigger Types Endp...
# 🖥│support-forum
d
I'm encountering an issue with the /api/v3/triggers_types/{slug} endpoint where some trigger payloads return incomplete schemas (e.g., attachment_list has items: {} and payload is just type: "object" for GMAIL_NEW_GMAIL_MESSAGE). This makes it difficult to programmatically extract all available fields for our CrewAI integration.
c
HI Ivan, Looks like we are getting the complete payload for this
GMAIL_NEW_GMAIL_MESSAGE
Could share your payload?
d
I think there's a misunderstanding. I AM getting the complete response from the API, but the schema definitions within that response are incomplete.
Let me show you another example that makes the issue clearer. Here's NOTION_PAGE_ADDED_TO_DATABASE:
The page field is just type: "object" with no properties defined
c
Thanks for the information you provided, could you specify your use case with the trigger schema?
d
We're building an agent system where users can reference trigger data in their agent instructions using interpolation
Copy code
jinja
Analyze the email {{step_1.subject}} and save attachment {{step_1.attachment_list[0].filename}}
Without complete schemas, we can't tell users what fields they can use. Right now we get: attachment_list has items: {} - empty, no field names page is type: "object" - no properties listed
We need the full schema to show available fields to users
c
It seems like the attachment_list is populated. As for the
NOTION_PAGE_ADDED_TO_DATABASE
the "type": object actually describes the keyword "**page**". I've attached some images for your reference. Let me know if the schema is not descriptive enough after considering the example payload. https://cdn.discordapp.com/attachments/1398683405880660028/1398713875062460547/Screenshot_2025-07-26_at_22.34.44.png?ex=68865d4e&is=68850bce&hm=9daea9c6dc2486df0de4cacee5c234f767a8d37c94baad40ff19d5c33b93048e& https://cdn.discordapp.com/attachments/1398683405880660028/1398713875410456757/Screenshot_2025-07-26_at_22.38.51.png?ex=68865d4e&is=68850bce&hm=e20271c4661d279b710c093eb4bbeb732c0dbd06629ad5c31516ea82bbf633cd&
a
Hey @dujusa, you're right about those incomplete schemas - definitely not ideal for extracting available fields programmatically. Just discussed with the team and we'll start working on more complete field definitions in the next couple of weeks.
d
@abhishekpatil4 , Any news on this?
a
hey Ivan. thanks for following up Not yet, definitely on our pipeline but might take sometime and will be picked once team has more bandwidth.