Planned
Add support for S3 action Nodes
Currently we only support S3 as a trigger. Add support to use it as a action node as well.

Aman Sharma 3 months ago
Planned
Add support for S3 action Nodes
Currently we only support S3 as a trigger. Add support to use it as a action node as well.

Aman Sharma 3 months ago
Resolved
Firecrawl > Agent Support
Problem: Current web scraping requires manual API integration and maintenance. Use case: Support business verification and structured data extraction directly within workflows. Functionality: Native Firecrawl agent tool with search, crawl, and extraction, plus automatic handling of authentication, rate limiting, and retries.

Aman Sharma 7 months ago
Resolved
Firecrawl > Agent Support
Problem: Current web scraping requires manual API integration and maintenance. Use case: Support business verification and structured data extraction directly within workflows. Functionality: Native Firecrawl agent tool with search, crawl, and extraction, plus automatic handling of authentication, rate limiting, and retries.

Aman Sharma 7 months ago
Planned
11Labs
Problem: Basic TTS/STT is insufficient for production-quality voice applications. Use case: Deliver high-quality, natural-sounding voice interactions for customer-facing apps. Functionality: A dedicated 11Labs node with full API coverage, streaming voice generation, configurable voices, and secure credential management.

Aman Sharma 7 months ago
Planned
11Labs
Problem: Basic TTS/STT is insufficient for production-quality voice applications. Use case: Deliver high-quality, natural-sounding voice interactions for customer-facing apps. Functionality: A dedicated 11Labs node with full API coverage, streaming voice generation, configurable voices, and secure credential management.

Aman Sharma 7 months ago
Resolved
GitHub Integration for Configuration and Code Sync
Add GitHub integration functionality to allow synchronization of prompt configurations, action definitions, and other code assets with a GitHub repository. This will streamline version control and collaboration workflows. Target completion within two months.

Aman Sharma 12 months ago
Resolved
GitHub Integration for Configuration and Code Sync
Add GitHub integration functionality to allow synchronization of prompt configurations, action definitions, and other code assets with a GitHub repository. This will streamline version control and collaboration workflows. Target completion within two months.

Aman Sharma 12 months ago
Resolved
Twilio Integration
Add Twilio integration functionality to Lematic to enable SMS communication capabilities. This will support sending and receiving messages within the AI-powered scam detection tool, allowing outreach and alerts to elderly users via SMS. This is a lower priority task but essential for expanding communication channels.

Aman Sharma 12 months ago
Resolved
Twilio Integration
Add Twilio integration functionality to Lematic to enable SMS communication capabilities. This will support sending and receiving messages within the AI-powered scam detection tool, allowing outreach and alerts to elderly users via SMS. This is a lower priority task but essential for expanding communication channels.

Aman Sharma 12 months ago
Resolved
Google Drive: set expectations, verify app, and narrow permissions
When adding Google Drive as a data source, Jason Reichle at 15:28 encounters a warning βGoogle hasnβt verified this appβ, but proceeds only with my encouragement. He then explains how he would like to limit granted access to a specific folder (Al Serize on 9/4 had same request). Recommended action Items to increase trust & reduce abandons: Set the userβs expectations before they get the warning. Update the email address referenced in the warning from vansha@lamatic.ai to admin@lamatic.ai (more trusted). Get Lamatic verified by Google. Limit permissions to something less than the entire Google Drive. #1 - Set Expectations: A simple way to boost trust is to explain the permissions theyβll be asked to grant in advance of the Google prompt (see highlighted area in the screenshot below). Suggested message text (for the highlighted area in the screenshot above): Add Credentials Add a unique name to reference this Credential within the workflow builder. Note: Google will ask you to grant lamatic.ai access to your Google Drive. This access is used strictly by the Lamatic application to allow you to create workflows using the information found on the authorized Google Drive. #2 - Update Lamatic app author Reference a more trusted email address than vansha@lamatic.ai on the warning below (e.g., admin@lamatic.ai). #3 - Get Lamatic verified by Google: Not sure what is required to do this, but getting verified would increase trust a lot. #4 - Narrow the permissions: Not sure if this is even possible, but the screen below is scary. Multiple users have requested that permissions be limited here to a specific folder (they have sensitive stuff in other folders and donβt want to grant access to this data).

cwhiteman almost 2 years ago
Resolved
Google Drive: set expectations, verify app, and narrow permissions
When adding Google Drive as a data source, Jason Reichle at 15:28 encounters a warning βGoogle hasnβt verified this appβ, but proceeds only with my encouragement. He then explains how he would like to limit granted access to a specific folder (Al Serize on 9/4 had same request). Recommended action Items to increase trust & reduce abandons: Set the userβs expectations before they get the warning. Update the email address referenced in the warning from vansha@lamatic.ai to admin@lamatic.ai (more trusted). Get Lamatic verified by Google. Limit permissions to something less than the entire Google Drive. #1 - Set Expectations: A simple way to boost trust is to explain the permissions theyβll be asked to grant in advance of the Google prompt (see highlighted area in the screenshot below). Suggested message text (for the highlighted area in the screenshot above): Add Credentials Add a unique name to reference this Credential within the workflow builder. Note: Google will ask you to grant lamatic.ai access to your Google Drive. This access is used strictly by the Lamatic application to allow you to create workflows using the information found on the authorized Google Drive. #2 - Update Lamatic app author Reference a more trusted email address than vansha@lamatic.ai on the warning below (e.g., admin@lamatic.ai). #3 - Get Lamatic verified by Google: Not sure what is required to do this, but getting verified would increase trust a lot. #4 - Narrow the permissions: Not sure if this is even possible, but the screen below is scary. Multiple users have requested that permissions be limited here to a specific folder (they have sensitive stuff in other folders and donβt want to grant access to this data).

cwhiteman almost 2 years ago
Resolved
Improve Documentation for Firecrawl
Documentation shows differently than how the feature is supposed to perform. Mismatches - Host URL Scrap vs Crawl Difference HTML Tags

Aman Sharma over 1 year ago
Resolved
Improve Documentation for Firecrawl
Documentation shows differently than how the feature is supposed to perform. Mismatches - Host URL Scrap vs Crawl Difference HTML Tags

Aman Sharma over 1 year ago