Plytix is an official, verified app on Make. Instead of manually configuring individual webhooks, you can connect your Plytix account directly and use a full set of ready-made modules to search, create, update, and delete products and assets, plus a real-time trigger that watches for product changes as they happen.
This article covers connecting Plytix to Make, the modules available once you're connected, and an alternative, more limited method using a generic webhook if you'd rather not connect the full app.
Building Plytix scenarios in Make with AI prompts
Alternative: Using a Generic Webhook for Channel Notifications
*Skip to any section in this article by clicking on the links above
Requirements
- A Plytix account. If you don't have one yet, check the Plytix pricing page.
- A Make account. Sign up for free if you don't have one.
- A Plytix API key and API password. You'll generate these as part of connecting the two, covered below.
⚠️ Only account Owners and Admins can view or manage API keys in Plytix.
Connecting Plytix to Make
Before you can use any Plytix modules in Make, you need to create a connection between the two, authenticated with a Plytix API key and password.
Step 1: Get your Plytix API key and password
1. Log in to your Plytix account.
2. Go to the Account Administration area. There are two ways to access:
- Go directly to accounts.plytix.com.
- Click your profile picture in the bottom-left corner of the platform, then click the Settings icon in your profile overview.
3. Then the API tab.
4. Click Create API key.
5. Copy the API key and API password values, and store them somewhere safe. You'll need both in the next step.
ℹ️ Learn more about generating API keys in API.
Step 2: Create the connection in Make
1. Log in to your Make account.
2. Add a Plytix module to your scenario.
3. Click Create a connection.
ℹ️ If the module you're adding has an instant tag (like the Watch Products trigger), click Create a webhook, then Create a connection.
4. Optional: in the Connection name field, enter a name for the connection.
5. In the API key field, enter the API key you copied from Plytix.
6. In the API password field, enter the API password you copied from Plytix.
7. Click Save.
8. If prompted, authenticate your account and confirm access.
You've successfully connected Plytix to Make, and can now use any Plytix module in your scenarios.
💡 To make changes to your connection later, see Make's guide to managing connections.
Available Modules
Once connected, these are the modules available for building your scenario:
Trigger
- Watch Products: triggers when a product is created or updated.
Products
- Search products: returns a list of products filtered by specified criteria.
- Get a product: returns information about a specific product by its product ID.
- Create a product: creates a new product.
- Update a product: updates a product.
- Delete a product: deletes a product.
Assets
- Search assets: returns a list of assets filtered by specified criteria.
- Get an asset: returns information about a specific asset by its asset ID.
- Upload an asset: uploads a new asset from a URL or file content.
- Delete an asset: deletes an asset.
Other
- Make an API call: sends a custom API call to Plytix, for endpoints not covered by the modules above.
ℹ️ This module list reflects what's available as of this article's writing. Make may add more Plytix modules over time, check the Plytix app page on Make for the current list.
Building Plytix scenarios in Make with AI prompts
You can describe the automation you want in plain language and let Make's AI build the scenario for you, instead of setting up every module by hand. Below are some example AI prompts for common Plytix workflows. Copy one, paste it into Make's AI assistant, and adjust the details (like your messaging app, project management tool, or spreadsheet) to match your setup.
These prompts are a starting point, not a fixed script. You can reword them, add steps, or combine them to fit how your team works.
Once Make builds the scenario, review each module before you turn it on. Check that your Plytix connection is selected, the right attributes are mapped, and any filters match the field names in your account.
Example AI prompts
1. Missing data alerts: Get notified when a product is missing key information.
"Build a Make scenario using the Plytix integration. When a product is updated in Plytix, filter for cases where the price is empty or the hero image is missing, and send an alert to my team's messaging channel with the product name and direct Plytix URL."
2. Launch handoffs between teams: Create tasks for other teams when a product's status changes.
"Create a Make scenario with Plytix. When a product status changes in Plytix, use a router: if the status is
Ready for Content, create a task in my project management tool with the product title, name, and price. If the status isLaunch Ready, send a launch message to Sales."
3. Weekly catalog audits: Get a scheduled report of products with incomplete data.
"Create a scheduled Make scenario that runs every Monday. Search Plytix for all products missing mandatory attributes (like dimensions, or completeness under 100%), write those product rows into a Google Sheet, and email a summary with the sheet link to my product manager."
4. Asset uploads from cloud storage: Send new files from a shared folder straight into Plytix DAM.
"Build a Make scenario triggered when a new file is uploaded to a specific Google Drive or Dropbox folder. Upload that file into Plytix DAM, attach it to the matching product SKU, and send a confirmation message to my design team."
5. AI-generated product descriptions: Turn supplier specs into product copy and write it back to Plytix.
"Build a Make scenario using Plytix. When a new SKU is detected in Plytix, fetch its specs from a spreadsheet, send those specs to [my preferred AI assistant] to write a product description, update the product in Plytix with the new text, create an approval task in my task manager, and send a Slack alert when it's approved."
Alternative: Using a Generic Webhook for Channel Notifications
If you'd rather not connect the full Plytix app, you can still get notified in Make when a specific Channel finishes processing, using a generic webhook instead. This is a narrower option: it only covers Channel processing notifications, not the broader product and asset automation the native app modules offer above.
Step 1: Create a webhook in Make
1. In your Make scenario, search for the Webhooks app, then select the Custom webhook module.
2. In the module's settings, click Add.
3. In the Webhook name field, enter a name for your webhook.
4. Click Save.
5. Make generates a webhook URL and immediately starts listening for requests sent to it. Copy this URL, you'll need it in the next step.
ℹ️ Each scenario needs its own webhook. You can't reuse the same webhook URL across multiple scenarios.
Step 2: Add the webhook URL to your Plytix Channel
1. In Plytix, go to the Channel you want to get notified about.
2. Click the Settings tab.
3. Find the Webhooks section.
4. Paste the webhook URL you copied from Make into the field provided.
5. Click Create.
Step 3: Test your webhook
1. Back in your Make scenario, click Run once. Make starts listening for an incoming request.
2. In Plytix, process the Channel you just added the webhook to.
3. Once processing finishes, Plytix sends a request to your webhook. Make automatically detects the structure of the data it receives, which makes it easier to map fields in the rest of your scenario.
Step 4: Add a module to act on the data
A webhook on its own only receives data, it doesn't do anything with it. To complete your automation, add another module after the Custom webhook module in your scenario, for whatever app you want to notify or update, for example, a Slack message, an email, or a new row in a Google Sheet, then map the fields from your webhook's data into that module.
💡 Most people use the native app's modules and the Watch Products trigger for anything involving product or asset data. This generic webhook method is really only useful if the specific thing you want to react to is a Channel finishing processing.
What's Next
- Learn how to create channels in Plytix
- Learn how to configure your account notification preferences
- Learn how to invite new users to your account