How it works
To move data from Microsoft SQL to Postgres PGVector Store automatically, use a ready-made scenario — no manual exports.
- Starts when: Schedule Trigger
- Then: Get slots
- Then: Append or update slot
- Then: Get lead
- Then: Append or update lead
- Then: Get human call
- Then: Append or update human call
- Then: Get human appointment
- Then: Append or update appointment
- Then: Booked Appointment
- Then: AI Summarizer1
- Then: Format output
- Then: Insert Lead
- Check: Check Appointment1
- If yes: save appointment - same service
- Check: If Appointment is ready
- If yes: save appointment - different service
- Then: AI Data Extractor
- Then: Output Format Text
- Check: Check Human is called
- If yes: Send Email Notification If Human is called
- Then: Add row for Human Call
- Then: Send via WhatsApp
- Then: Pinecone Vector Store
- Then: Default Data Loader
- Then: Recursive Character Text Splitter
- Then: Get a document
- Starts when: When clicking ‘Execute workflow’
- Then: Embeddings OpenAI
- Then: Vector Store Tool
- Then: Pinecone Vector Store (Retrieval)
- Then: Embeddings OpenAI1
- Starts when: Verify • WA (hub.challenge)
- Check: filter text messages
- If yes: Prepare Text Data
- Then: Insert Row Memory
- Then: Get History
- Then: Get only users appointment
- Then: Format Context
- Then: Main AI Agent
- Then: Update Row
- Then: Get leads
- Check: Check if Lead
- Check: If Audio
- If yes: Get Audio
- Then: Download Audio
- Then: Transcribe Audio
- Check: If Image
- If yes: Get Image
- Then: Download Image
- Then: Analyze image
- Then: Edit Fields
- Check: If Video/PDF
- If yes: Get file
- Then: Download file
- Then: Prepare Email With Attachment
- Then: Send Email with attachment
- Then: Simple Memory
- Starts when: WhatsApp Webhook
- Then: OpenAI Chat Model
You can launch this Microsoft SQL + Postgres PGVector Store integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.