Post a Daily Stock Price to Slack with Make and a Scraping API
A stock quote page is easy to read by hand and tedious to check every morning. This guide turns that routine into a small Make scenario: a scraping API fetches a Yahoo Finance quote page, CSS extraction rules pull the name, price, change, and change percent, and a Slack module posts the result into a channel you choose. You can then schedule the scenario to run daily.
What you will build
The workflow has two modules. The first is a scraping API module in Make that makes an API call to a Yahoo Finance quote URL and returns structured fields. The second is a Slack module that creates a message in a channel such as #stock-alerts. A schedule controls how often the scenario runs.
Before you start, confirm three things: you have your own scraping API key, you can create or log into a Make account, and you have a Slack channel you are allowed to post to. The guide uses Tesla's quote page at https://finance.yahoo.com/quote/TSLA as the example URL; any other Yahoo Finance stock page follows the same pattern.
Step 1: Get your scraping API key
If you do not already have an account, sign up at the provider's registration page. Once you are in, copy your API key from the account dashboard. Keep the key out of screenshots and shared documents. In Make, the key is stored inside a connection rather than typed into every module, so you enter it once.
Step 2: Create a new Make scenario
Log in to Make and create a new scenario. A scenario is a chain of modules that pass data between services. Click the first plus sign, choose the scraping API as the app, and pick the Make an API call action from the list. You will then be asked to create a connection or select an existing one.
Step 3: Create a scraping API connection
Make uses connections for services that need authentication. Click Add, then paste the API key you copied from your account dashboard. Once the connection is saved, the module can use it for every run without you re-entering the key.
Step 4: Configure the scrape action
Set the method to GET. Browsers use GET to load pages, and this scrape does not submit a form, so POST is not needed. Enter the Yahoo Finance quote URL you want to watch; the example uses the Tesla page.
Open Show advanced settings and find Extract Rules (JSON). The rules below map a short field name to a CSS selector on the quote page. The complete rule set is supplied as a protected module and should be used exactly as given; do not retype or paraphrase the selectors.
Extraction field map
The four keys in the rule set correspond to the parts of the quote header you will want in the Slack message. Use this map when wiring the Slack text field:
- name — the company name shown in the quote header
- price — the current regular market price
- change — the absolute change in price
- change-percent — the percentage change
If a key comes back empty, the selector did not match the page at that moment. That is a different problem from an authentication error, which usually appears at the connection stage, and from a scenario that never runs, which usually means scheduling was not switched on.
Should you enable Render JS?
The source workflow marks Render JS as optional and recommends leaving it off for this scrape. The scraping API's documentation describes rendering as a paid feature that consumes extra credits; confirm current credit terms in your account before relying on it. A quick checklist:
- Quote data appears in the page HTML: keep Render JS off.
- Fields come back empty after a page change: test once with Render JS on before committing to it.
- You are watching many symbols: keep rendering off to control credit use.
Step 5: Test the scrape
Use the Run Once button at the bottom of the page to execute the module while you build. Check that the output contains the four fields with values rather than empty strings. If the output is empty, revisit the URL and the extraction rules before moving on to Slack.
Step 6: Configure the Slack module
Add a Slack connection; Make will redirect you to Slack to authorize it. For this workflow it does not matter whether the connection acts as a bot or as a user. Click the plus sign again, choose Slack, and select Create a message.
Pick the target channel by ID or name. The example uses a channel called #stock-alerts selected from the list. In the text field, compose the message and insert the scraping API output fields where you want the values to appear. The layout is yours; the important part is that the field names match the extraction keys.
Example message
Using the Tesla quote page as the source, a message built from the four fields could read: name, price, change, and change-percent on one line, followed by the quote URL. Save the scenario and run it again; the message should arrive in the chosen channel. If the message posts but the numbers are blank, the Slack mapping is fine and the extraction step needs attention.
Step 7: Schedule the scenario
Open the scenario detail page and find the Schedule tab under Options. Choose Scheduling, then click the clock icon over the scraping API module and set Run Scenario to Every day. Pick the time you want the update to arrive.
Finally, switch Scheduling on. Without that switch, the scenario will not run automatically no matter what schedule you configured.
Frequently asked questions
Do I need JavaScript rendering for a Yahoo Finance quote page?
No. The guide marks Render JS as optional and recommends leaving it off. Only turn it on if the fields stop appearing in the returned HTML, and check your credit terms first, since rendering is billed as an extra feature.
The Slack message arrives but the price fields are empty. What should I check?
The extraction step is the likely cause. Confirm the quote URL is correct and that the Extract Rules (JSON) selectors still match the page. An empty field means the selector did not find the element, which is separate from a connection or scheduling failure.
Why does my scenario not run on schedule?
Scheduling must be switched on in the scenario options. Setting Run Scenario to Every day and choosing a time is not enough on its own; the scheduling toggle has to be enabled.
Should the Slack connection be a bot or a user?
Either works for this workflow. The guide notes that the choice does not matter for the purpose of posting a stock update to a channel.
{
"name" : "#quote-header-info h1.D\\(ib\\).Fz\\(18px\\)",
"price" : "#quote-header-info [data-field=\"regularMarketPrice\"]",
"change" : "#quote-header-info [data-field=\"regularMarketChange\"]",
"change-percent" : "#quote-header-info [data-field=\"regularMarketChangePercent\"]",
}