Integration Flows

Integration flows let you connect Verk with your favorite tools to automate data synchronization and create powerful cross-platform workflows. Build automation that spans multiple services without writing code.

Prerequisites

Before creating integration flows, ensure you have:

• Admin or Member role in your organization
• Connected integrations (Slack, GitHub, Google Calendar, etc.)
• API keys or webhooks for external services (if required)
• Understanding of the data you want to sync

Connect your first integration

Start by connecting an external service:

1. Navigate to Settings → Integrations
2. Browse available integrations or search for your tool
3. Click Connect on the integration you want to add
4. Follow the OAuth authorization flow or enter API credentials
5. Grant required permissions
6. Click Authorize to complete connection

Available integrations

Verk connects with 20+ popular tools across different categories:

Communication tools

Project management

Development tools

Productivity tools

File storage

Create integration flows

Build workflows that connect multiple tools:

Two-way sync flow

Synchronize tasks between Verk and external tools:

1. Navigate to Settings → Integration Flows
2. Click Create Flow
3. Select Two-Way Sync template
4. Configure source and destination:

• Source: Verk project
• Destination: GitHub repository

5. Map fields between platforms:

• Verk Priority → GitHub Label
• Verk Status → GitHub State
• Verk Assignee → GitHub Assignee

6. Set sync frequency (real-time, hourly, daily)
7. Click Create & Enable

Trigger-based flow

Execute actions when events occur:

1. Choose Trigger-Based Flow template
2. Select trigger event:

• Task status changed
• New comment added
• File uploaded
• Due date approaching

3. Add conditions to filter events
4. Define actions in external tools:

• Post Slack notification
• Create Google Calendar event
• Update Jira issue
• Send email via Outlook

5. Test flow with sample data
6. Enable flow for production

Scheduled flow

Run workflows on recurring schedules:

1. Select Scheduled Flow template
2. Set execution schedule:

• Daily at specific time
• Weekly on selected days
• Monthly on specific date

3. Configure data queries:

• Tasks due this week
• Completed tasks yesterday
• Overdue tasks by project

4. Define export actions:

• Generate report in Google Sheets
• Send summary to Slack channel
• Update Notion database

5. Save and schedule flow

Field mapping

Map data between Verk and external platforms:

Status mapping

Translate statuses across different systems:

Configure custom mappings in Integration Settings → Field Mapping.

Priority mapping

Align priority systems:

Custom field mapping

Map project-specific fields:

• Budget (Currency) → Jira "Story Points"
• Client Name (Text) → Asana "Client" tag
• Sprint (Dropdown) → Linear "Cycle"
• Approval Status (Checkbox) → Monday.com "Status" column

Common integration patterns

Slack notifications

Send updates to Slack channels automatically:

Flow configuration:

• Trigger: Task status changed to "Done"
• Condition: Project is "Product Development"
• Action: Post to #engineering Slack channel
• Message format: Custom template with task details

Message template:

 Task completed: `{{task.title}}`
Assignee: @`{{task.assignee}}`
Project: `{{task.project}}`
Duration: `{{task.time_spent}}`

GitHub issue sync

Keep Verk tasks synchronized with GitHub issues:

Bi-directional sync:

• GitHub issue created → Verk task created
• Verk task updated → GitHub issue updated
• GitHub issue closed → Verk task marked done
• Comments sync in both directions

Field mappings:

• Issue title ↔ Task title
• Issue body ↔ Task description
• Issue labels ↔ Task labels
• Issue assignees ↔ Task assignee
• Issue milestone → Task project

Calendar integration

Sync task deadlines with Google Calendar:

Flow setup:

• Trigger: Task with due date created/updated
• Action: Create/update Google Calendar event
• Event details:
• Title: Task title
• Description: Task description + link
• Time: All-day event on due date
• Attendees: Task assignee
• Reminders: 1 day before, 1 hour before

Email to task

Convert emails into tasks automatically:

Email forwarding setup:

1. Enable email integration in Settings
2. Get your unique Verk email address: tasks+project@yourorg.verk.com
3. Configure email rules:

• Subject → Task title
• Body → Task description
• Attachments → Task files
• CC recipients → Task watchers

4. Set default project or use email suffix for routing

Smart parsing:

• Extract due dates from email text
• Identify priority keywords (urgent, important)
• Auto-assign based on recipient or keywords
• Parse checklist items from bullet points

CRM integration

Update external CRM when deals close:

Flow trigger: Custom field "Deal Stage" = "Closed Won"

Actions:

1. Send webhook to CRM API with deal data
2. Create onboarding project in Verk
3. Assign account manager
4. Send welcome email to customer
5. Post notification to #sales Slack channel
6. Create recurring tasks for customer success

Webhook integration

Use webhooks for real-time data exchange:

Incoming webhooks

Receive data from external services:

1. Navigate to Settings → Webhooks
2. Click Create Webhook
3. Name your webhook (e.g., "Stripe payments")
4. Copy webhook URL
5. Configure in external service
6. Define webhook actions:

• Create task from webhook data
• Update existing tasks
• Trigger automation rules
• Send notifications

Webhook URL format:

https://api.verk.com/webhooks/v1/{organization_id}/{webhook_id}

Sample payload handling:

{
  "event": "payment_received",
  "customer": "Acme Corp",
  "amount": 5000,
  "invoice_id": "INV-2024-001"
}

Verk action:

• Create task in "Finance" project
• Title: "Process payment from {customer}"
• Add custom field with {amount}
• Link to invoice {invoice_id}
• Assign to finance team

Outgoing webhooks

Send data from Verk to external services:

1. Create automation rule or flow
2. Add "Send Webhook" action
3. Configure webhook:

• URL: External service endpoint
• Method: POST, PUT, or PATCH
• Headers: Authentication, content type
• Body: JSON payload with task data

4. Test webhook delivery
5. Enable error notifications

Payload template:

{
  "task_id": "`{{task.id}}`",
  "title": "`{{task.title}}`",
  "status": "`{{task.status}}`",
  "assignee": "`{{task.assignee.email}}`",
  "project": "`{{task.project.name}}`",
  "timestamp": "`{{current_time}}`"
}

Data synchronization

Sync strategies

Choose the right sync approach for your workflow:

Real-time sync:

• Changes propagate immediately
• Uses webhooks for instant updates
• Best for: Critical workflows, time-sensitive data
• Requires: Stable webhook connections

Scheduled sync:

• Runs at specific intervals (hourly, daily, weekly)
• Batches multiple updates
• Best for: Reports, analytics, non-urgent data
• More reliable for large datasets

Manual sync:

• User-triggered synchronization
• Full control over sync timing
• Best for: One-time migrations, data verification
• Allows review before sync

Conflict resolution

Handle conflicting updates gracefully:

Last write wins:

• Most recent change takes precedence
• Simple but may lose data
• Best for: Single-direction primary source

Manual resolution:

• Flag conflicts for human review
• Preserve both versions
• Best for: Critical data, collaborative editing

Field-level merge:

• Combine non-conflicting field updates
• Prompt for conflicts only
• Best for: Complex objects, multiple editors

Custom rules:

• Define priority by field or source
• Example: Verk controls status, GitHub controls assignee
• Best for: Specific business logic

Bulk data import

Migrate existing data from other platforms:

Import wizard

Use the import wizard for one-time migration:

1. Navigate to Settings → Import Data
2. Select source platform (Jira, Asana, Trello, etc.)
3. Authenticate with source account
4. Choose projects/boards to import
5. Map fields between platforms:

• Match custom fields
• Map statuses and priorities
• Preserve assignees and dates

6. Preview import with sample data
7. Run import (background process)
8. Review import report

Supported import formats:

• Native integrations (OAuth-based)
• CSV files with custom mapping
• JSON exports from API
• Excel spreadsheets

Import options

Configure import behavior:

• Preserve IDs: Keep original task IDs if possible
• Import comments: Include historical comments
• Import attachments: Download and migrate files
• Import history: Preserve creation/update timestamps
• Link relationships: Maintain task dependencies
• Archive completed: Mark old tasks as archived

Integration monitoring

Track integration health and performance:

Sync status dashboard

Monitor active integrations:

• Connection status: Online, offline, authentication issues
• Last sync: Time of most recent synchronization
• Sync success rate: Percentage of successful operations
• Error count: Failed sync attempts
• Data volume: Number of items synced

Access from Settings → Integrations → Monitoring

Error handling

Manage sync failures:

Automatic retry:

• Failed syncs retry with exponential backoff
• Maximum 3 retry attempts
• Errors cleared after successful sync

Error notifications:

• Email alerts for persistent failures
• In-app notifications for sync issues
• Slack alerts for critical integrations

Error log:

• View detailed error messages
• See affected tasks and data
• Timestamps and retry history
• Manual retry option

Rate limiting

Respect API limits:

• Monitor usage: Track API calls against limits
• Throttling: Automatic rate limiting
• Queuing: Batch requests during high activity
• Alerts: Notification when approaching limits

Troubleshooting

Integration not connecting

Common connection issues:

1. Authentication expired

• Reconnect integration
• Re-authorize with OAuth
• Update API credentials

2. Permission denied

• Check OAuth scopes
• Verify account permissions
• Confirm workspace access

3. API endpoint changed

• Check integration status page
• Update Verk integration
• Contact support if persistent

Data not syncing

Sync troubleshooting steps:

1. Check sync status

• View integration dashboard
• Review last sync time
• Check error logs

2. Verify field mapping

• Ensure fields exist in both systems
• Check data type compatibility
• Validate required fields

3. Test with sample data

• Create test task
• Trigger sync manually
• Review sync results

4. Review filters

• Check project filters
• Verify condition logic
• Ensure data matches criteria

Duplicate items

Prevent duplicate task creation:

Enable deduplication:

• Match by external ID
• Check title similarity
• Compare creation timestamps
• Link instead of create new

Clean up duplicates:

1. Identify duplicate pairs
2. Choose primary version
3. Merge data from duplicate
4. Delete or archive duplicate
5. Update integration mapping

Performance issues

Optimize slow integrations:

• Reduce sync frequency: Change from real-time to hourly
• Limit data scope: Sync only active projects
• Filter old data: Exclude archived tasks
• Batch operations: Group multiple updates
• Use selective sync: Choose specific fields only

Best practices

Plan your integration strategy

Before connecting integrations:

1. Map your workflow: Understand data flow between tools
2. Identify single source of truth: Choose primary data owner
3. Define sync boundaries: Decide what to sync and what to keep separate
4. Document field mappings: Record custom field relationships
5. Plan for conflicts: Establish resolution rules

Start small and scale

Build integrations incrementally:

1. Connect one integration at a time
2. Test with small dataset first
3. Validate data accuracy
4. Monitor for issues
5. Expand to full dataset
6. Add additional integrations

Monitor and maintain

Keep integrations healthy:

• Check sync status weekly
• Review error logs regularly
• Update field mappings when workflows change
• Test after platform updates
• Clean up unused integrations

Secure your integrations

Protect sensitive data:

• Use least privilege access for API keys
• Rotate credentials periodically
• Monitor integration access logs
• Revoke unused integration permissions
• Enable two-factor auth on connected accounts

Optimize performance

Maintain fast sync speeds:

• Sync only necessary data
• Use field-level updates instead of full object
• Schedule heavy syncs during off-hours
• Archive old data to reduce dataset size
• Monitor API rate limits

Common use cases

Development team workflow

Sync engineering tools:

Integrations:

• GitHub for code and issues
• Slack for team communication
• Linear for sprint planning

Flow:

1. GitHub issue created → Verk task created in "Development"
2. Task assigned → Notify assignee in Slack
3. Status "In Review" → Create Linear story for QA
4. Task completed → Close GitHub issue, post to #wins channel

Customer support pipeline

Manage support requests across tools:

Integrations:

• Email forwarding for ticket creation
• Slack for team coordination
• Notion for knowledge base
• Zendesk for customer facing

Flow:

1. Email received → Task created with customer details
2. Auto-assign to support rep (round-robin)
3. Status "Needs Info" → Send email to customer
4. Status "Resolved" → Update Zendesk ticket
5. Common issue → Create Notion documentation

Marketing campaign management

Coordinate marketing workflows:

Integrations:

• Google Calendar for campaign schedules
• Slack for team updates
• Google Drive for assets
• Asana for cross-team coordination

Flow:

1. Campaign task created → Create calendar events
2. Assets uploaded → Share to Google Drive folder
3. Review complete → Update Asana board
4. Launch date → Notify #marketing channel
5. Campaign ends → Generate report, share results

Sales pipeline automation

Track deals end-to-end:

Integrations:

• CRM (Salesforce, HubSpot) for lead data
• Google Calendar for meetings
• Slack for team notifications
• DocuSign for contracts

Flow:

1. Lead qualified → Create deal task in "Sales Pipeline"
2. Meeting scheduled → Sync to Google Calendar
3. Proposal sent → Trigger DocuSign workflow
4. Deal won → Create onboarding project
5. Notify teams → Post to Slack, update CRM

Related documentation

• Automation Rules
• Webhooks
• API Reference
• Slack Integration
• GitHub Integration