How to add Slack to Deltek Costpoint
Short answer
Build a small Slack app that sits beside Costpoint: it reads approvals and project data through supported interfaces, posts interactive messages, and relays decisions back to Costpoint's workflow. Slash commands give quick, read-only lookups. Check first whether your data and Slack plan are allowed to mix.
Slack is less common than Teams among Costpoint customers, but it is widely used in engineering-led contractors, newer defense tech companies and commercial manufacturers that run Costpoint for project accounting. Their pain is the same: Costpoint is where the money is tracked, Slack is where the project talks, and the two do not meet.
A useful Slack integration is small. It does a few things well: pushes decisions to the right person, answers a handful of lookups, and posts alerts into the project channel. It does not mirror the Costpoint screens.
If you handle CUI or ITAR data, the first question is whether your Slack plan and workspace are even permitted to hold it. Many teams use Slack only for non-controlled logistics and financial status, and keep the rest in authenticated links.
What teams use it for
Slash command for open commitments
A command like /commit PROJECT returns open PO and subcontract commitments for a project, limited to what the caller may see.
Interactive purchase approvals
Block Kit message with Approve and Reject buttons for requisitions waiting in a manager's Costpoint queue.
Project channel cost alerts
Post when a task's actual cost passes a percentage of its budget, so engineers see overrun risk without waiting for a monthly review.
Receiving and inspection updates
Tell the build team when a long-lead part is received so planning can release the work order.
Customer billing readiness
Tell the billing analyst when a billing period's prerequisites are complete, such as approved timesheets and posted vouchers.
Deltek Costpoint integration surface
- Costpoint web services where licensed: confirm available objects and authentication for your version and hosting.
- Reporting views or a replica on SQL Server for on-prem installs: the right source for lookups and threshold jobs.
- Costpoint workflow approvals and notification emails: usable as a trigger feed for the Slack app.
- Scheduled reports and flat file exports: a low-risk path for daily digests.
- Standard import utilities: a controlled path to write accepted changes, preserving validations.
How it works
- 1
Create the Slack app
Set up bot scopes, a slash command and interactivity URL. Use Socket Mode only for development; production should use signed HTTPS requests.
- 2
Map Slack users to Costpoint users
Maintain a table of Slack member IDs to Costpoint user IDs and project roles, updated by SSO group or HR feed.
- 3
Build query handlers
Each slash command calls a fixed, parameterized query with the caller's project list applied as a filter.
- 4
Wire approval events
Poll the workflow source, send Block Kit messages, and process the button click by verifying the signature, user and pending state.
- 5
Add rate limits and retries
Respect Slack's rate limits, deduplicate alerts, and back off when Costpoint is in maintenance.
Example flows
Lookup by slash command
Trigger: An engineer types /commit PROJ-100 in a channel.
- Slack sends a signed request; the app verifies it within the time window.
- App maps the user and checks access to PROJ-100.
- It runs the commitments query and returns an ephemeral message with totals and top open POs.
Result: Quick answers visible only to the asker, with no Costpoint login.
Budget overrun nudge
Trigger: Nightly job finds a task at 90 percent of budget.
- Query actual and budget by task from a reporting view.
- Check last alert band to avoid repeating.
- Post to the project channel with the task, percent, and a link to the Costpoint screen.
Result: Engineers and the PM act before the overrun becomes an invoice problem.
Keeping data on-prem
Slack is a hosted service, so keep Costpoint and the app server on your network and have the app reachable only via the HTTPS endpoint Slack needs. Do not send raw cost data through a third-party automation tool. For natural language on top, run an open-weight model locally and use it to pick from your fixed set of queries rather than to generate SQL. If you work under CUI rules, confirm Slack's government offering or your own policy before putting any controlled data in channels.
Security checklist
- Verify Slack request signatures and timestamps on every callback.
- Never trust a Slack user ID alone for write actions; confirm mapping and current Costpoint role.
- Respond to sensitive lookups as ephemeral messages, not channel posts.
- Keep bot tokens in a secrets store and rotate them; limit scopes to what is used.
- Disable file upload handling unless needed; do not pass attachments into Costpoint.
Ways to get it done
Slack Workflow Builder with exports
Effort: Days.
Daily digests and reminders with no write-back.
Custom Slack app over Costpoint interfaces
Effort: 3 to 6 weeks for a first release.
Interactive approvals and lookups under your security model.
Netray build
Effort: Pilot in weeks, scope per workflow.
Slack front end with on-prem model, governed queries and reviewed writes.
Pitfalls
- !Public channel posts that expose vendor pricing or subcontract values to staff without need to know.
- !Slash commands that time out after three seconds because the query is slow; acknowledge first, respond later.
- !Alert storms when a threshold hovers around a limit; use bands and cooldowns.
- !Ignoring Costpoint maintenance windows, which causes failed approvals.
- !Letting a model write ad hoc SQL for Slack questions.
Frequently asked questions
Is there a ready-made Slack app for Deltek Costpoint?
We know of no widely used first-party Slack app. Third-party connectors may exist, but most teams use a small custom app or a workflow tool fed by Costpoint exports. Ask your reseller what is current for your version.
Can we approve Costpoint items inside Slack?
Yes, if the decision is passed to Costpoint's workflow through a supported interface and recorded under the approver's identity. The Slack click is only the signal; the Costpoint record is the audit trail.
Should project cost data go in Slack?
Only if your policy allows it. Cost data on government contracts can be sensitive, so many teams post counts and statuses in channels and put amounts behind an authenticated link or an ephemeral reply.
Slack or Teams for Costpoint?
Use whichever your people actually live in. Teams usually fits better if you are on Microsoft 365 GCC High; Slack suits engineering-heavy teams already there. The Costpoint adapter is largely the same either way.
Can AI answer free-form questions in Slack?
Yes, but safely by mapping the question to approved queries and running them as the asking user, with the model only formatting the result. Letting it query live tables freely risks wrong or unauthorized answers.
Want Slack working on your Deltek Costpoint?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment