Skip to content

Feature/workflowmodel #59

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Vamsi-o merged 2 commits into from
Jan 21, 2026
Merged

Feature/workflowmodel #59

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5f40d06
feat: add user workflows component and API integration
Vamsi-o Jan 21, 2026
d6b0dad
fix: update webhook trigger description for clarity
Vamsi-o Jan 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions JSON STRUCTURES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
Email Input :

Comment on lines +1 to +2
Copy link

@coderabbitai coderabbitai bot Jan 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Incomplete documentation file.

This file was committed with only a label "Email Input :" but no actual JSON structure documentation. Either add the intended JSON structure examples or remove this placeholder file to avoid confusion.

🤖 Prompt for AI Agents 
In `@JSON` STRUCTURES.md around lines 1 - 2, The file contains only the
placeholder label "Email Input :" and lacks the intended JSON schema or
examples; either populate it with the concrete JSON structure(s) for the
expected "Email Input" (include required fields, types, example values, and
optional fields) or delete the file to avoid confusion — update the document by
replacing the placeholder label with the complete JSON structure and at least
one example payload so reviewers and consumers can rely on it.

9 changes: 9 additions & 0 deletions apps/web/app/lib/api.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,15 @@ import z from "zod";
import { getCredentials } from "../workflow/lib/config";
// Wrap all API calls in async functions and make sure to set withCredentials: true and add Content-Type header.
export const api = {
user: {
get: async () => {
return await axios.get(`${BACKEND_URL}/user/workflows`,
{
withCredentials: true,
headers: { "Content-Type": "application/json" },
})
}
},
workflows: {
create: async (name: string, Config: any) =>
await axios.post(
Expand Down
2 changes: 1 addition & 1 deletion apps/web/app/workflows/[id]/components/ConfigModal.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ export default function ConfigModal({
const [config, setConfig] = useState<Record<string, any>>({});
const [loading, setLoading] = useState(false);
const userId = useAppSelector((state) => state.user.userId) as string;

// console.log("This is the credential Data from config from backend" , config);
// Fetch credentials with hook based on node config (google, etc) if appropriate
let credType: string | null = null;
if (selectedNode) {
Expand Down
Loading
Loading