Make.com Integration Tutorial

This tutorial walks you through setting up the Make.com extension to automate workflows between Kiket and Make.com (formerly Integromat).

What You'll Build

By the end of this tutorial, you'll have:

• Kiket issues automatically triggering Make.com scenarios
• Make.com scenarios creating issues in Kiket
• Workflow guards that validate automation completion before transitions
• Automation suggestions based on issue content

Prerequisites

• A Kiket workspace with admin access
• A Make.com account with API access
• Basic familiarity with webhooks and REST APIs

Step 1: Install the Make.com Extension

Via Marketplace

1. Navigate to Settings > Extensions > Marketplace
2. Search for "Make.com Integration"
3. Click Install
4. Grant the requested permissions:
5. issues:read - Read issue data for automation
6. issues:write - Create/update issues from Make
7. comments:write - Post automation status as comments
8. workflows:read - Analyze workflows for automation opportunities

Via CLI

kiket extensions install dev.kiket.ext.make

Step 2: Configure Make.com Credentials

Get Your Make.com API Key

1. Log in to Make.com
2. Go to Profile > API
3. Generate a new API token with these scopes:
4. scenarios:read
5. scenarios:execute
6. webhooks:write

Get Your Webhook URL

1. In Make.com, create a new scenario
2. Add a Webhooks > Custom webhook module as the trigger
3. Copy the webhook URL (e.g., https://hook.make.com/abc123xyz)

Configure in Kiket

1. Navigate to Settings > Extensions > Make.com Integration
2. Enter your credentials:

Setting	Description
MAKE_API_KEY	Your Make.com API token
MAKE_WEBHOOK_URL	The webhook URL from your Make scenario
AUTO_TRIGGER_ENABLED	Set to true to auto-trigger on transitions
MAX_RETRIES	Number of retry attempts (default: 3)

1. Click Save

Step 3: Create Your First Automation

Scenario: Customer Onboarding

Let's create an automation that triggers when an issue moves to "Ready for Automation".

In Make.com:

1. Create a new scenario called "Kiket Customer Onboarding"
2. Add modules:
3. Webhooks > Custom webhook (trigger)
4. Google Sheets > Add a Row (or your preferred action)

5. Slack > Send a Message (optional notification)

6. Configure the webhook to expect this payload:

   {
     "issue_key": "PROJ-123",
     "title": "Customer onboarding request",
     "description": "Set up new customer account",
     "labels": ["customer", "onboarding"],
     "custom_fields": {}
   }
   

7. Save and activate the scenario

In Kiket:

1. Create a workflow state called ready_for_automation
2. Add a transition from backlog to ready_for_automation
3. Create an issue with:
4. Title containing "customer" or "onboarding"

5. Labels: automation

6. Transition the issue to "Ready for Automation"

The extension will: 1. Detect the transition 2. Analyze the issue content 3. Match it to the "Customer Onboarding Flow" scenario 4. Trigger the Make.com webhook 5. Post a comment with the execution status

Step 4: Set Up Bidirectional Integration

Creating Issues from Make.com

The extension provides a REST API for Make to create issues in Kiket.

In Make.com:

1. Add an HTTP > Make a request module
2. Configure:
3. URL: https://your-extension-url/api/issues
4. Method: POST
5. Headers:
   • Content-Type: application/json
   • Authorization: Bearer YOUR_KIKET_TOKEN
6. Body:

   {
     "project_key": "PROJ",
     "title": "Auto-created from Make",
     "description": "This issue was created by a Make.com scenario",
     "labels": ["automation", "make"],
     "custom_fields": {
       "source_scenario_id": "{{scenario.id}}"
     }
   }
   

Example: Lead Capture Flow

1. Trigger: Google Forms submission
2. Action 1: Create Kiket issue with lead details
3. Action 2: Send Slack notification
4. Action 3: Add to CRM

Google Forms → Make.com → Kiket Issue + Slack + CRM

Step 5: Add Workflow Guards

Prevent issues from being marked "Done" until automation completes.

Configure the Guard

1. Add the requires-automation label to issues that need automation verification
2. The extension automatically checks Make.com execution status before allowing transitions to done

Guard Responses

Status	Effect
allow	Transition proceeds
pending	Transition blocked, shows "Automation in progress"
deny	Transition cancelled, shows error message

Example Workflow

# workflow.yaml
states:
  - id: backlog
  - id: in_progress
  - id: ready_for_automation
  - id: done

transitions:
  - from: ready_for_automation
    to: done
    guards:
      - extension: dev.kiket.ext.make
        event: workflow.before_transition
        required: true

Step 6: Use Scenario Templates

The extension includes pre-built scenario templates that match based on keywords:

Template	Triggers On	Use Case
Customer Onboarding	customer, onboarding, welcome, signup	New customer setup flows
Support Ticket Routing	support, ticket, bug, help	Route support requests
Order Fulfillment	order, fulfillment, shipping, warehouse	E-commerce automation
Data Sync	sync, import, export, migration	Data movement tasks

How Matching Works

1. Extension analyzes issue title, description, and labels
2. Calculates confidence score for each template
3. Triggers the best match above the confidence threshold (default: 70%)

Customizing Templates

Edit lib/scenario_matcher.rb to add your own templates:

SCENARIO_TEMPLATES = {
  'my_custom_scenario' => {
    name: 'My Custom Workflow',
    triggers: ['keyword1', 'keyword2', 'keyword3'],
    confidence_threshold: 0.7
  }
}

Step 7: Monitor Automations

View Execution History

Use the command palette (Cmd/Ctrl + K) and search for: - View Automation History - See recent Make.com executions

Check Extension Logs

1. Navigate to Project > Extensions > Activity
2. Filter by "Make.com Integration"
3. View detailed logs for each webhook delivery

Metrics to Watch

• Scenario trigger success rate
• Average execution time
• Failed scenario count
• Retry attempts

Step 8: Advanced Patterns

Pattern 1: Conditional Routing

Route issues to different scenarios based on labels:

# In app.rb
sdk.register('issue.transitioned') do |payload, context|
  issue = payload['issue']

  scenario = case
    when issue['labels'].include?('urgent')
      'urgent_escalation'
    when issue['labels'].include?('customer')
      'customer_onboarding'
    else
      'default_processing'
  end

  make_client.trigger_scenario(scenario_id: scenario, data: issue)
end

Pattern 2: Approval Workflows

Require Make.com approval before transitions:

sdk.register('workflow.before_transition') do |payload, context|
  # Check external approval system via Make
  approval = make_client.check_approval(issue_key: payload['issue']['key'])

  case approval['status']
  when 'approved'
    { status: 'allow', message: 'Approved by manager' }
  when 'pending'
    { status: 'pending', message: 'Awaiting manager approval' }
  else
    { status: 'deny', message: 'Not approved' }
  end
end

Pattern 3: Scheduled Automations

Combine with Make.com's scheduler for recurring tasks:

1. Create a Make scenario with Schedule trigger
2. Add HTTP > Make a request to query Kiket API
3. Process issues matching your criteria
4. Update issues or trigger notifications

Troubleshooting

Scenario Not Triggering

1. Verify AUTO_TRIGGER_ENABLED is true
2. Check that issue transition matches expected state (ready_for_automation)
3. Review extension logs for errors
4. Ensure Make API key has correct permissions

Webhook Signature Errors

1. Verify KIKET_WEBHOOK_SECRET matches between Kiket and extension
2. Check that payload hasn't been modified in transit
3. Ensure timestamp is within acceptable window

Low Confidence Matches

1. Add more specific keywords to issue titles
2. Lower the confidence threshold in scenario templates
3. Create custom templates for your use cases

Make.com Rate Limits

1. Enable exponential backoff (default)
2. Set appropriate MAX_RETRIES value
3. Consider batching multiple operations

Next Steps

• Explore the Extension API Reference
• Learn about Custom Data Modules
• Set up Scheduled Reports with Make.com delivery

Resources

• Make.com Documentation
• Kiket Extension SDK
• Example Extension Repository