Memara Trigger: New Memory
AI-generatedOverview
This node triggers a workflow when new memories appear in a Memara space by polling the Memara API. It fetches memories based on specified filters such as tags, source, and minimum importance, and emits new memories that have appeared since the last poll. This is useful for automating workflows that need to react to new data entries in Memara, such as notifications, data processing, or integrations with other systems.
Use Case Examples
- Trigger a workflow every time a new memory with specific tags is added to Memara.
- Poll Memara for new memories from a particular source and process them automatically.
Properties
| Name | Meaning |
|---|---|
| Poll Times | Specifies the schedule for polling Memara to check for new memories, with options for various intervals and custom cron expressions. |
| Limit | Maximum number of memories to fetch per poll, between 1 and 100. Higher values reduce the chance of missing rapid bursts but increase payload size. |
| Tags | Optional comma-separated tags to filter memories; only memories matching all listed tags are returned. |
| Source | Optional source filter passed to the list memories API to restrict results. |
| Minimum Importance | Optional minimum importance filter (1–10). Use 0 to disable this filter. |
Output
JSON
json_memaraTrigger- Internal flag indicating the memory was triggered as a new memory event.
Dependencies
- Memara API with an API key credential for authentication
Troubleshooting
- If no new memories are detected, ensure the polling schedule is correctly configured and the filters (tags, source, minimum importance) are not too restrictive.
- API rate limits may be reached if polling too frequently or with a high limit; adjust polling frequency or limit accordingly.
- Errors related to authentication indicate issues with the Memara API credentials; verify and update credentials as needed.