Fix Fireflies search_meeting input: date was renamed to start_time - #23
Merged
Merged
Conversation
The live catalog no longer has a 'date' input on FirefliesCLIAPI.search.search_meeting — the schema now exposes start_time/end_time DATETIME fields, so the CI audit fails on every PR. Verified against list-action-input-fields on 2026-07-31.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
examples/by-pattern/notify-on-event/meeting-to-action-items/workflow.ts:date→start_timeWhy
dateinput onFirefliesCLIAPI.search.search_meeting— the current schema hasstart_time/end_timeDATETIME fields (verified withlist-action-input-fieldstoday)INPUT_MISSING, which currently failscli-and-sdk-smokeon every PR (main last passed July 20, before the schema drifted)event.startmaps cleanly ontostart_time; workflow typechecks under the same flags CI uses🤖 Generated with Claude Code