Skip to main content

Zapier integration

Zapier lets you connect ProcureIQ to the tools your team already uses every day. You can use it to notify Slack when large orders arrive, update a CRM when a payment succeeds, create Trello cards for new support tickets, or search ProcureIQ products from spreadsheet-driven workflows.

This guide walks through the full setup in plain English, including how to connect your account, how ProcureIQ triggers work in Zapier, and how to build a real example Zap from start to finish.

What you can automate with ProcureIQ and Zapier​

Common ProcureIQ + Zapier automations include:

  • sending order alerts to Slack or Microsoft Teams
  • creating CRM follow-up tasks after successful payments
  • opening internal tickets when customer support issues are created
  • searching products from form responses or spreadsheets
  • creating support tickets from customer intake forms
  • forwarding key business events into data warehouses or reporting tools

ProcureIQ supports both:

  • polling triggers for simple Zapier workflows
  • webhook-based triggers for faster, near real-time workflows

Prerequisites​

Before you start, make sure you have:

  • a ProcureIQ account
  • a Zapier account
  • permission to create OAuth applications or API integrations inside your ProcureIQ workspace if your team restricts developer access
  • a clear idea of the ProcureIQ events you want to automate, for example order.created or payment.succeeded

ProcureIQ connection details for Zapier​

When Zapier asks for ProcureIQ OAuth settings, use:

  • Authorization URL: https://app.procureiq.com/oauth/authorize
  • Token URL: https://api.procureiq.com/oauth/token
  • Scopes: orders:read orders:write products:read support:read

If you are building a private Zapier app, you can also use the repository guide and app definition here:

  • docs/integrations/zapier/README.md
  • docs/integrations/zapier/zapier-app-definition.json

Step 1: Connect ProcureIQ to Zapier​

1. Create or open your Zapier app​

In Zapier:

  1. Open My Apps or the Zapier Platform developer console.
  2. Choose Add connection or create a new private integration.
  3. Select OAuth 2.0 as the authentication method.

2. Enter the ProcureIQ OAuth settings​

Fill in the ProcureIQ endpoints listed above.

Use the recommended scopes unless you need a narrower permission set. For example:

  • orders:read if you only need to read order data
  • orders:write if the Zap will create orders
  • products:read if the Zap searches product listings
  • support:read if the Zap reads support tickets

3. Copy the Zapier redirect URL​

Zapier will give you a redirect URL during the OAuth setup. Add that URL to the list of allowed redirect URIs in your ProcureIQ OAuth app settings.

Screenshot placeholder: Zapier app settings showing the ProcureIQ authorization URL, token URL, and redirect URI.

4. Sign in and approve access​

When you test the connection:

  1. Zapier will redirect you to ProcureIQ.
  2. Sign in to your ProcureIQ account.
  3. Review the requested permissions on the ProcureIQ consent screen.
  4. Click Allow.
  5. Zapier will store the access token and complete the connection.

Screenshot placeholder: ProcureIQ OAuth consent screen showing app name, permissions, and the Allow button.

5. Name the connection clearly​

If your team manages multiple ProcureIQ accounts, give the Zapier connection a clear name such as:

  • ProcureIQ Production
  • ProcureIQ West Africa Sales
  • ProcureIQ Support Workspace

That makes it much easier to select the correct account later.

Step 2: Using ProcureIQ triggers in Zapier​

ProcureIQ triggers can be configured in two ways:

  • Polling triggers: Zapier checks ProcureIQ every 15 minutes for new records
  • REST hooks: ProcureIQ sends events to Zapier immediately through webhooks

If you need near real-time behavior, prefer webhooks. If you want something simple and low-maintenance, polling is often enough.

Trigger: New Order Created​

What it means: the trigger fires when a new order is created in ProcureIQ.

Polling endpoint pattern:

GET /api/v1/orders?since={{lastPolled}}&limit=10

Good use case: notify your team on Slack when a new order arrives.

Example flow:

  1. Trigger: New Order Created
  2. Action: Slack - Send Channel Message
  3. Map fields:
    • Slack channel: #sales-orders
    • Message text:
New ProcureIQ order received.
Order ID: {{orderId}}
Customer: {{userId}}
Total: {{totalAmount}} {{currency}}
Items: {{itemCount}}

Helpful tip: if you only want large orders, add a Zapier filter step such as:

  • totalAmount Greater than 500

Trigger: Payment Succeeded​

What it means: the trigger fires when a ProcureIQ payment is confirmed successfully.

Polling endpoint pattern:

GET /api/v1/payments?status=SUCCESS&since={{lastPolled}}

Good use case: update a CRM record after payment is collected.

Example flow:

  1. Trigger: Payment Succeeded
  2. Action: HubSpot - Update Deal
  3. Map fields:
    • Deal ID: look up from your CRM reference field
    • Payment status: Paid
    • Amount paid: {{amount}}
    • Paid date: {{paidAt}}

Helpful tip: if your CRM expects a sales owner or internal order reference, use a lookup step before the update so you can match the ProcureIQ order ID to the correct CRM record.

Trigger: Support Ticket Created​

What it means: the trigger fires when a new support ticket is created in ProcureIQ.

Polling endpoint pattern:

GET /api/v1/support/tickets?since={{lastPolled}}

Good use case: create a Trello card for customer support triage.

Example flow:

  1. Trigger: Support Ticket Created
  2. Action: Trello - Create Card
  3. Map fields:
    • Board: Customer Support
    • List: New Tickets
    • Card title: {{ticketNumber}} - {{subject}}
    • Description:
Category: {{category}}
Priority: {{priority}}
Status: {{status}}
User: {{userId}}

Helpful tip: use separate lists for urgent or payment-related tickets if you want Zapier to route them differently.

Step 3: Using ProcureIQ actions in Zapier​

ProcureIQ actions let Zapier send data into ProcureIQ, not just read from it.

Action: Search Products​

What it does: searches ProcureIQ products from a Zap and returns matching listings.

Good use case: look up product options when a new Google Sheets row is added.

Example flow:

  1. Trigger: Google Sheets - New Spreadsheet Row
  2. Action: ProcureIQ - Search Products
  3. Map fields:
    • Search term: {{Sheet Column: searchTerm}}
    • Country: {{Sheet Column: country}}
    • Limit: 10

You can then use the search results to:

  • send the top products by email
  • append matches back to the spreadsheet
  • create internal tasks for a sourcing team

Action: Create Support Ticket​

What it does: creates a new ProcureIQ support ticket.

Good use case: turn a support form submission into a tracked ProcureIQ ticket.

Example flow:

  1. Trigger: Typeform - New Entry or Webflow Forms - Form Submission
  2. Action: ProcureIQ - Create Support Ticket
  3. Map fields:
    • Subject: {{Form Subject}}
    • Category: ACCOUNT
    • Priority: NORMAL
    • Message: {{Form Description}}

You can add a confirmation step after that, such as sending the user a follow-up email with the ticket number.

Step 4: Example Zap - When a large order is placed, send a Slack message​

This example combines a ProcureIQ trigger, a filter, and a Slack message.

Goal​

When a ProcureIQ order greater than $500 is created, notify your team in Slack.

Step-by-step​

1. Create a new Zap​

In Zapier:

  1. Click Create Zap
  2. Name it Large ProcureIQ Order Alert

2. Choose the trigger​

  1. Select ProcureIQ
  2. Choose New Order Created
  3. Connect your ProcureIQ account
  4. Test the trigger and pull in sample order data

3. Add a filter​

  1. Add a new step
  2. Choose Filter by Zapier
  3. Configure:
    • Left side: totalAmount
    • Condition: Greater than
    • Right side: 500

This ensures only large orders continue.

4. Add the Slack action​

  1. Add a new step
  2. Choose Slack
  3. Select Send Channel Message
  4. Choose your Slack workspace and channel

Use a message like this:

Large ProcureIQ order placed

Order ID: {{orderId}}
Customer ID: {{userId}}
Total: {{totalAmount}} {{currency}}
Items: {{itemCount}}
Created at: {{createdAt}}

5. Test the Zap​

Use a recent ProcureIQ order as test data. Confirm:

  • the filter blocks small orders
  • Slack receives the right fields
  • values are formatted in a way your team can read quickly

6. Publish the Zap​

Turn the Zap on once the test succeeds.

Screenshot placeholder: Zapier multi-step workflow showing ProcureIQ trigger, Filter by Zapier, and Slack action.

Troubleshooting​

Here are the most common ProcureIQ + Zapier issues and how to fix them.

OAuth connection fails​

Symptoms:

  • Zapier cannot finish authentication
  • ProcureIQ rejects the redirect
  • you see an invalid redirect URI error

Fixes:

  • confirm the exact Zapier redirect URL is registered in your ProcureIQ OAuth app
  • make sure you are using the production ProcureIQ auth URLs
  • confirm the ProcureIQ OAuth app is active

Trigger returns no data​

Symptoms:

  • the Zap tests successfully but finds no orders, tickets, or payments

Fixes:

  • create a fresh ProcureIQ event after turning on the Zap
  • confirm your account has permission to read the selected resource
  • check whether the Zap is using polling instead of a webhook and wait for the next poll cycle

Slack or CRM fields look empty​

Symptoms:

  • the Zap runs but the downstream message is missing values

Fixes:

  • re-test the ProcureIQ trigger to refresh sample data
  • re-map the fields after updating the trigger
  • check whether the event payload actually includes the field you are using

401 or 403 errors​

Symptoms:

  • Zapier says the ProcureIQ request is unauthorized or forbidden

Fixes:

  • reconnect the ProcureIQ account in Zapier
  • confirm the OAuth scopes include the resource you are trying to access
  • verify the ProcureIQ user account still has access to the workspace data

Duplicate notifications​

Symptoms:

  • your Slack, CRM, or task board receives repeated events

Fixes:

  • prefer REST hooks over polling where possible
  • add a deduplication step using the ProcureIQ event ID or order ID
  • make sure your workflow only watches newly created records, not all updated records

Rate limit considerations for Zapier polling​

ProcureIQ applies API rate limits per API key or OAuth client, so it is worth designing Zapier flows carefully.

Good practices​

  • keep polling intervals at Zapier defaults unless you truly need more frequent sync
  • request only the fields and endpoints you need
  • use webhooks instead of polling for high-volume event streams
  • add filters early so later Zap steps do not run unnecessarily

Why this matters​

Polling triggers can add up quickly if you have:

  • many Zaps using the same ProcureIQ account
  • high-frequency polling across multiple workspaces
  • multiple actions after each trigger

If you expect large volumes, move critical flows to:

  • ProcureIQ outbound webhooks
  • n8n or Make webhook-based automations
  • custom webhook consumers for maximum control

Next steps​

Once your first Zap is working, good next automations to build are:

  • create a CRM task when payment.failed occurs
  • notify operations when order.shipped fires
  • create an internal ticket when support.ticket_created is urgent
  • sync approved merchant products into your catalog or reporting tools

If you need more control than Zapier offers, the next best guide is n8n or Custom Webhook Consumer.