render-lab-tasks-intercom
Python port of all 10 registered tasks in the pinned TypeScript pack at
45f9c2d44bd28e01ae9813e0d2ff56ee6c533816. Python 3.12+.
From the repository, install this pack and its supporting core together:
pip install render-lab-tasks-intercom==0.1.0
Import task definitions from render_lab_tasks_intercom.tasks. Combine its app with
other pack apps using Workflows.from_workflows(...) and call tasks with
await ctx.run(task, input). Package roots do not register tasks. JSON fields
retain the TS spelling; Python functions use snake_case.
Tasks
| Registered name | Python export (also exposes _impl) |
|---|---|
intercom.addNote |
add_note |
intercom.assignConversation |
assign_conversation |
intercom.closeConversation |
close_conversation |
intercom.createTicket |
create_ticket |
intercom.getContact |
get_contact |
intercom.getConversation |
get_conversation |
intercom.reply |
reply |
intercom.searchConversations |
search_conversations |
intercom.tagUser |
tag_user |
intercom.updateContact |
update_contact |
Dependencies and retries
Raw implementations accept context first and keyword-only deps. The .client
module exports typed Port, Deps, and Client classes (also vendor-named aliases).
Inject a fake port, or pass a caller-owned httpx.AsyncClient to Client for custom
transport/configuration. Default dependencies close their HTTP clients after the
operation. Credentials resolve at first use. HTTP and SDK retries are disabled;
retry.py owns durable retry settings. DTO types live in .types.
Environment
| Variable | Contract |
|---|---|
INTERCOM_ACCESS_TOKEN |
Required on API calls. |
Verification and limitations
The reply and ticket payloads preserve the pinned TS surface. The limited ticket DTO does not expose ticket type configuration; reply does not expose adminId (addNote does). Validate these inherited limitations against your Intercom account before live use.
Shared JSON fixtures compare the Python task output with the actual pinned TS implementation. REST fixtures also compare HTTP requests; HubSpot and Linear fixtures compare source SDK arguments with HTTP payloads/GraphQL variables. No live vendor calls were made for this batch. Registered-task parity does not claim live readiness or all supporting TS exports. See the root verification tracker and docs/porting-batches.md. Licensed under MIT.
Webhook adapter
render_lab_tasks_intercom.webhooks.intercom_adapter(on_event, ...) returns a
registration-free adapter for render_lab_triggers. The callback receives the
verified event and returns {"task": "namespace.task", "args": [event]} or None.
The signing credential INTERCOM_CLIENT_SECRET is read inside verification unless
provided explicitly. Importing this module does not register tasks. Signature
checks use the raw body; live delivery remains in the testing backlog.
1 maintainer
Metadata
1 maintainer
Release files for render-lab-tasks-intercom 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| render_lab_tasks_intercom-0.1.0.tar.gz | 6.8 kB | With provenance | Details for render_lab_tasks_intercom-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| render_lab_tasks_intercom-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for render_lab_tasks_intercom-0.1.0-py3-none-any.whl |
Total release size: 19.9 kB
Release files / render_lab_tasks_intercom-0.1.0.tar.gz
| Download URL | render_lab_tasks_intercom-0.1.0.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3411f8230ffd938e7452f19deaf54547a39d2836aa38d65b20a72d7735600c39
|
|
BLAKE2b-256 checksum How to use checksums |
b597899d31dc1be05c8c7610e729a62f3695807421595c9acc7aeb1929a8762a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logRelease files / render_lab_tasks_intercom-0.1.0-py3-none-any.whl
| Download URL | render_lab_tasks_intercom-0.1.0-py3-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d61aae8469c48462aa9aeee55c2b2902113795bdee8f6792fd55959ac89bc44f
|
|
BLAKE2b-256 checksum How to use checksums |
23a1aa064502c1f1cbcbb4232263d5a11a2fe569332bf3ccb61fbd89af76304a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logSecurity for render-lab-tasks-intercom 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for render_lab_tasks_intercom-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
