Attend the November AIforce AMA: Give Coding Agents Real Org Context with Catalog and MCP Join this interactive and engaging Ask Me Anything with our experts to learn how Salesforce Catalog, Metadata Grounding, and MCP Servers give coding agents the context to explore your data model, trace lineage, and check the impact of changes before you build. Bring your questions and get them answered live. Join the event on …

Channel
Salesforce Developers India
@salesforcedevsindia
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Polls · Telegram's recommendations · Cite this entry
23,335subscribers
-312 since we began measuring on 28 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001182917303 |
|---|---|
| Type | Channel |
| Username | @salesforcedevsindia |
| Description | Official channel for Salesforce Developers in India and Asia Pacific run by the Salesforce Developer Relations team. Subscribe to receive updates on key announcements, live coding sessions, webinars, events, and a whole lot more! |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 September 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/salesforcedevsindia |
Topic
Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 13 October 2026 and assigned it the closest of 31 fixed categories, at 50% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 21:58 | 23,335 | -18 |
| 11 Nov 2026, 21:36 | 23,353 | -6 |
| 8 Nov 2026, 19:26 | 23,359 | -22 |
| 7 Nov 2026, 11:57 | 23,381 | -15 |
| 6 Nov 2026, 09:01 | 23,396 | -7 |
| 5 Nov 2026, 10:25 | 23,403 | +4 |
| 4 Nov 2026, 11:01 | 23,399 | -19 |
| 3 Nov 2026, 14:26 | 23,418 | -7 |
| 2 Nov 2026, 11:17 | 23,425 | -4 |
| 1 Nov 2026, 14:36 | 23,429 | -2 |
| 31 Oct 2026, 16:36 | 23,431 | -10 |
| 30 Oct 2026, 17:15 | 23,441 | -9 |
| 29 Oct 2026, 19:39 | 23,450 | -5 |
| 28 Oct 2026, 18:17 | 23,455 | -10 |
| 27 Oct 2026, 19:48 | 23,465 | -8 |
| 26 Oct 2026, 18:58 | 23,473 | -2 |
| 25 Oct 2026, 22:27 | 23,475 | -6 |
| 24 Oct 2026, 21:26 | 23,481 | -3 |
| 23 Oct 2026, 18:06 | 23,484 | -5 |
| 22 Oct 2026, 18:46 | 23,489 | first reading |
Engagement
24 posts held, back to 31 March 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 71 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.53%
- avg views ÷ 23,335 subscribers
- Avg views / post
- 1,290
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 24 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 24 (31 March 2026 – 16 November 2026) |
| Views total | 2,583 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 15:01 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
- Photos
- 425
- Videos
- 26
- Links
- 397
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 10s
- Average length
- 10s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
⚡ Tomorrow: Free & Virtual AIforce Workshop on Wednesday, Nov. 4 Join us for Get Hands-on with AIforce, a free virtual workshop where you’ll explore out-of-the-box AIforce skills and learn to build custom experiences that extend Salesforce into new agentic surfaces like Claude, Slack, and more. Get hands-on with Salesforce MCPs, plugins, and skills to bring your Salesforce data, workflows, and functionality into the…
Salesforce Developers India pinned a photo
📢 Join us for a rare opportunity to connect with Salesforce's senior leadership — an exclusive gathering for Trailblazers across India to converse about their journey and its road ahead through a panel discussion. 🗓️ October 5th 📍 ITC Kohenur, A Luxury Collection Hotel, Hyderabad Register now to save your spot: https://sforce.co/4zdfRPY #Trailblazer #Salesforce #Agentblazer #Community
📅 This Week: #DF26 Developer Keynote on Thursday, September 17 Join us in person at Dreamforce in San Francisco or stream live on Salesforce+ for a first look at what’s next for developers, including AIforce, AI-powered innovations, and live demos. - Sept 17 | 9:00 a.m. PT - Add to your in-person agenda: sforce.co/3UdjR3y - Stream on Salesforce+: sforce.co/46cH7RX
📅 #DF26 Developer Keynote on September 17W hether you're joining us in person or tuning in from home, join us for a first look at what’s next for developers, including Headless 360, AI-powered innovations, and live demos.* Sept 17 | 9:00 a.m. PT* Add to your in-person agenda: sforce.co/3UdjR3y * Stream on Salesforce+: sforce.co/46cH7RX
A Free Hands-On Security Workshop for Admins In this virtual workshop, you'll get hands-on to build practical security expertise, learn how to proactively protect your org, and stay current on security tools. Register Now
Salesforce Developers India pinned a photo
Ready to go headless? The Salesforce Headless 360 Workshop is coming to Hyderabad on July 18, 2026, as a free, in-person experience built for developers who want to go deep on Salesforce Headless 360. Here's what you need to know: • 🆓Free event — no cost to attend • ✅Approval-based registration — complete the prerequisites and your spot gets confirmed • ⏳Limited seating — approvals are granted on a first-come, fir…
🚀 New workshop alert! We've replaced Agentforce Vibes Workshops with Hands On with Salesforce Headless 360 — a free virtual workshop covering how to build headless experiences and enterprise apps with Salesforce Hosted MCPs and Agentforce Vibes. ✨ Any frontend. Any experience. Powered by MCP. 📅 Next session: July 1 at 10:30AM SGT / 1:30PM AEST with @Aditya Naag Topalli 👉Register now
The Agentforce In Action Challenge is now live — and your build deserves a spotlight. If you've been building with Agentforce, the Agentforce In Action Challenge is for you. 1⃣ Record a 3–5 min demo of your agent 2⃣ Post publicly on LinkedIn with #AgentforceInAction, tag @Trailhead 3⃣ Submit the form. Win an Apple Watch Ultra. Inspire the next wave of Agentblazers. All orgs welcome — yes, even Dev Edition. 🔗 For ful…
Salesforce Developers India pinned a GIF
Showing the 12 most recent of 24 posts we hold for @salesforcedevsindia. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Polls
The 4 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Which of the following captures the core idea behind Salesforce Headless 360 ?
- get rid of APIs16%
- APIs for humans and agents55%
- Limit agent data access10%
- Rebuild workflows for AI18%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
How do child components access a shared state manager?
- mportState()8%
- getState()57%
- fromContext()24%
- useManager()12%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
What does "..." mean when used as an action input value?
- Input is optional26%
- Input is null22%
- LLM assigns it - Slot filling32%
- gets from a parent action21%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
In Data360, what is NOT a feature of zero copy?
- User is only responsible for source data23%
- Data only accurate as of last sync point28%
- Data remains in original location27%
- No data movement cost21%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 24 most recent posts we hold, published 31 March 2026 to 16 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@SanjayGuptaTechSchool · 7,933#1
@salesforceinterview · 5,216#2
@ttutechzoneforfreshers · 5,216#3
@sfdcpanther · 6,786#4
@salesforcegeek · 11,751#5
@apexHours · 4,425#6
@muleyindia · 3,353#7
@Salesforcekeeda · 4,899#8
@cloudgyatasolutions · 476#9
@OLW_Clausecraft · 1,054#10
@snowflakecomputing · 6,844#11
@ApacheSparkDevelopers · 7,903#12
@lwindiaofficial · 7,534#13
@Freshersbaba · 4,958#14
@ProjectsWithSourceCode · 2,497#15
@cpp_programming_books · 5,388#16
@Rajesh_Mall_Officiall · 1,727#17
@CodeWithKT · 14,987#18
@Techvine · 5,434#19
@available_IT_candidates · 2,098#20
@Hilega_Milega_FAN_CLUB · 328#21
@DarlingCrazyfan · 517#22
@PARahulSirTestbook · 1,882#23
@zensajnaniofm · 565#24
@itfreelancers · 26,678#25
@retard_meme_posting · 2,588#26
@JavaJobs4u · 3,986#27
@centreforretailinvestors · 1,181#28
@CodingNews · 22,608#29
@Sen_Academy · 1,998#30
@jobs_supports · 2,457#31
@TradingLife0001 · 1,716#32
@datasciencefree · 68,643#33
@PixelHubUpdates · 12,939#34
@bharat_voice · 8,289#35
@bdscience · 3,547#36
@FUNLEARNINGACTIVITY · 2,666#37
@neville · 1,327#38
@Khidkii · 291#39
@cryptoandstockss · 440#40
@ShitalGK · 1,934#41
@StockMarketWisdom · 467 (as read 28 September 2026)#42
@WebBooksUz · 460 (as read 28 September 2026)#43
@specializedkinesiology · 1,991#44
@wcpl_2026 · 5,706 (as read 28 September 2026)#45
@EVandCC_CHANNEL · 2,545#46
@demon_slayer_wallpapers_4k · 2,351#47
@enscape_3d_channel · 2,746#48
@curaj_2009 · 962#49
@All_PRIME_LEAK_prime_leaker · 399#50
@amanxcricketprimeleakk · 559 (as read 28 September 2026)#51
@lebhainotes · 2,678#52
Read from Telegram’s recommendation API, most recently 28 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@jobspand · 19,560
Telegram ranks this channel #47 of 73 here — alongside 72 others — read 28 September 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 14 November 2026 — this entry's latest reading, not the date you are reading this.
“Salesforce Developers India” (@salesforcedevsindia), 23,335 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/salesforcedevsindia.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.