Devin.LinQ: Custom Nodes for Lovable/Replit & Make Integration
Hi! I'm building an AI automation stack using Lovable.dev (Frontend/SEO), Replit (Deep Learning Backend), and N8N/Make (Logic).
I have 3 questions regarding your tool's capabilities:
Custom Entities: Since my services are self-built, can I create custom blocks with my own names and icons for Lovable and Replit, instead of just standard SaaS logos?
Project Specifics: Can I create distinct workflows for different projects? For example, labeling one node "Project A Frontend" and another "Project B Frontend" while connecting them to the same backend?
Renaming & Annotations: In Make/N8N, my backend calls are generic "HTTP Requests". Can I rename these nodes in Puzzle to something specific like "Replit DL Engine" and add annotations to explain the operational logic?
I need to ensure I can map my custom architecture clearly. Thanks!
b_ragone
Jan 26, 2026A: Hey Devin, happy to answer these questions.
1. Custom Entities — the way I'd recommend you upload those tools using whatever name you call that tool from an internal or external branding perspective. For contrast, I don't call Puzzle GitHub just because the code is hosted there, I call it Puzzle because that's the tool's name. The tool directory moderators will likely remove any duplicate uploads of similarly named tool entries like "Replit App" or "Custom Lovable App", for example.
2. Yes you can create distinct workflows for different projects, then use the "Go-to" step to connect those disparate maps.
3. If our moderators saw "Replit DL Engine", it'd likely be taken down as a duplicate of Replit. Typically https level documentation goes within the step notes of a Replit assigned step.