Hello Careerflow, I'm writing to request support for outbound webhooks for your CRM-like Job Tracker pipeline, so that customers like me can stream job/board events to our own systems. My hope is to enable consolidated job tracking across platforms. Careerflow is currently the only application web app I use that does not allow me to forward updates from your application to custom software in real time. Use Case: I use multiple platforms and tools during the job search process. While your Job Tracker board is an excellent interface for managing roles through stages, I also need an automated way to synchronize job records and status changes into a central tracking system for analytics, reminders, and cross-platform consolidation. Today, without webhooks, my only options are manual exports, which is not timely and creates unnecessary overhead. Requested Capability: Add configurable outbound webhooks that notify a user-defined endpoint whenever meaningful events occur to jobs or the board. Key Events to support: 1: Job Created (e.g. added to tracker) 2: Job updated (e.g. field changes such as title) 3: Job stage changed (e.g. moved between board columns) 4: Job deleted/archived 5: Interview/Task scheduled or updated Payload Contents (Job and Context) Ideally, each webhook would include the following: 1: Event metadata a: event_type (e.g. job.stage_changed) b: event_id (UUID for uniqueness) c: occurred_at (ISO timestamp) d: version (payload schema version) 2: Job Identifiers a: job_id (stable internal ID) 3: Job Details a: title b: company_name c: location (e.g. remote/hybrid/on-site + city/country if available) d: job_url e: source_platform f: applied_at (ISO timestamp) g: key status fields (e.g., current_stage, stage_id, stage_name) 4: Stage Move Details a: from_stage b: to_stage Including both IDs and human-readable names reduces follow-up API calls and makes downstream processing simpler. Configuration Capabilities: Ideally, configuration would include the following: Ability to create one or more webhook subscriptions Selection for which event types to receive Ability to set a destination URL Ability to set a shared secret for signature verification Delivery Capabilities: 1: Standard approach for idempotency and deduplication (e.g. unique event_id, X-Webhook-Id header or similar) 2: webhook delivery logs (success/failure, response code, last attempt) Why This Matters: Webhooks would unlock real-time synchronization to personal CRMs, Notion/Airtable, and personal analytics pipelines, enabling users to not only leverage AI in our job application process in order to gain an edge in the competitive job market, but also leverage statistics and analytics in order to understand what is working and what is not working, without having to maintain cumbersome excel spreadsheets or employ manual methods for data extraction. If it would be helpful, I am happy to provide sample endpoints and confirm payload structures from an integration standpoint. Thank you for considering this feature request.
