Resources · Make integration

800.com Make integrationAutomate 800.com with Make.

Can a phone call in 800.com start work in your other tools? The 800.com Make integration gives you 2 triggers that watch your calls. This guide is for teams that live on the phone, and it walks you from the connection to a first working scenario.

Try the 800.com integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the 800.com Make integration do?

The 800.com Make integration links your 800.com account to Make, a tool where you build a scenario (an automation made of connected steps) without writing code. Here 800.com is the starting point: when a call starts or ends, Make picks it up at its next check and hands it to the next step you choose.

A call log that fills itself. Watch Call Completed picks up every finished call. Add a spreadsheet or CRM module after it and each call becomes a row your sales team can read later, instead of a note someone forgets to type.

A heads up while the phone rings. Watch Call Started reacts to calls that begin. Paired with a chat app, it can tell the right channel that a call is in progress, so nobody picks up the same lead twice.

A follow up after the call. Starting from Watch Call Completed again, a support team can open a task in its project tool so the promised callback never slips.

Know the limits before you plan. 800.com only offers these 2 triggers in Make: no action to place a call, no search, and no Make an API Call module. The official doc lists both triggers without describing them, so check what each bundle contains with a first test. Many apps also have an n8n node, so check whether 800.com does; the n8n vs Make comparison helps you pick. New to the tool? Start with the Make review or the Make training.

Connect

How do you connect 800.com to Make?

  1. 01

    Get your API key ready

    The doc asks for an active 800.com account and an API key. Create the account on 800.com first if you have none, and keep the key at hand: Make will ask for it once, then every module reuses the same connection.

  2. 02

    Add a module and create the connection

    In your scenario, add a 800.com module and click Create a connection. You can give the connection a name, which helps when a colleague shares the same Make team or when you link more than one account.

  3. 03

    Paste the key and save

    Paste the key that 800.com gives you in the field Make shows, then click Save. The connection now appears in the module, ready for both triggers, and you will not have to enter the key again.

First scenario

Your first scenario with 800.com

GoalWhen a call ends in 800.com, Make passes it to the tool where your team keeps its records.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to place the first module on the empty canvas.

  2. 02

    Pick Watch Call Completed

    Search for 800.com, choose Watch Call Completed and select the connection you created. This module (one brick of the scenario) will open the flow each time a call is over.

  3. 03

    Add where the call goes

    Click the + on the right of the trigger and pick the app that stores your records. Map the call data from the trigger into its fields, one bundle (one call) at a time.

  4. 04

    Test with Run once

    Click Run once, which runs the scenario one time. Open the bubbles to read the bundles each module received, and confirm the call data landed where you expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default. Then switch the scenario on. Each module run counts as an operation on your Make plan.

Triggers

What starts a 800.com scenario

2 modules start a scenario when something happens in 800.com. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by 800.com as soon as it happens.

800.com1Watch Call Completed

Watch Call Completed

triggerIn the docs only

Get every finished call from 800.com into your scenario, so the details of the conversation can go straight to a log, a CRM or a task list. Each call arrives as one bundle that the next modules can use.

How it fires
scheduled, Make checks the app on the scenario's schedule. Its type is inferred from its name in the doc, so check for the clock badge in your editor; with a schedule, calls reach Make at the next check.
When to use it
any follow up that makes sense only once the conversation is over, like logging the call or planning a callback.
Watch out
the doc does not describe this module, so run it once and read the bundle before you map anything.
800.com2Watch Call Started

Watch Call Started

triggerIn the docs only

Catch calls as they begin in 800.com, so your team knows a line is busy or a lead is already being handled. Each new call becomes a bundle you can send to a chat channel or a shared board.

How it fires
scheduled, Make checks the app on the scenario's schedule. On the Free plan the shortest gap between two checks is 15 minutes, 1 minute on paid plans.
When to use it
alerts about calls in progress, when you need the start of the conversation rather than its end.
Watch out
by the time Make checks, the call may already be over; pick Watch Call Completed when the outcome matters.
Need help

Need help automating 800.com with Make?

A person reads every message.

FAQ

Questions about 800.com and Make

01Is the 800.com Make integration free?
Yes, on the Make side. 800.com is a standard app, available from the Free plan. That plan allows 2 active scenarios, checks no more often than every 15 minutes, and runs each scenario for up to 5 minutes. Paid plans Core, Pro, Teams and Enterprise lower the gap to 1 minute and remove the cap on active scenarios. You still need your own active 800.com subscription, which the doc points to on the 800.com pricing page; this page gives no price for either tool.
02What do you need to connect 800.com to Make?
Two things: an active 800.com account and an API key from 800.com. The official doc gives no connection steps of its own, so you follow the usual Make path. Add a 800.com module, click Create a connection, name it if you like, paste the key and click Save. Both triggers then reuse that same connection, so you only enter the key once per account. If you manage several 800.com accounts, create one named connection for each.
03Does the 800.com trigger react in real time?
No. The doc does not state their type, but their names point to scheduled triggers (check for the clock badge): Make checks 800.com on the scenario's schedule rather than being called by the app. A new scenario runs every 15 minutes by default. The Free plan keeps that 15 minute minimum, while paid plans can go down to 1 minute, which brings calls into Make faster without making them instant. To see a call right away while testing, click Run once in the editor.
04What if the 800.com module you need is missing in Make?
It depends on what is missing. The 800.com app in Make only watches calls: it has no action, no search and no Make an API Call module, so you cannot place a call or look one up from a scenario. The doc also warns that its own content is AI-generated from the 800.com documentation and may contain mistakes. For anything beyond the 2 triggers, another app or the Hackceleration team can help you design a workaround.
05Should you use Make or n8n for 800.com?
It depends on the tool your team already uses. Many apps have an n8n node as well as a Make app; check whether 800.com has one before you compare. In Make you get the 2 triggers described here, a visual editor and the Free plan to test. Compare how each tool fits your other apps and your team's habits, rather than looking for a winner, and test with a real call first.
Same platform

Other docs you might need on this stack.

Browse all integrations